Multi-function thermostat with health monitoring features

ABSTRACT

A multi-function thermostat for a building includes a communication interface and a processing circuit. The communications interface is configured to communicate with an emergency server and receive occupant health data from one or more health sensors configured to monitor an occupant of the building. The processing circuit is configured to determine a health metric associated with the occupant based on the occupant health data and cause the communications interface to send a distress message to the emergency server when the health metric associated with the occupant indicates a medical emergency.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application claims the benefit of and priority to U.S. ProvisionalPatent Application No. 62/247,672 filed Oct. 28, 2015, U.S. ProvisionalPatent Application No. 62/274,750 filed Jan. 4, 2016, U.S. ProvisionalPatent Application No. 62/275,202 filed Jan. 5, 2016, U.S. ProvisionalPatent Application No. 62/275,204 filed Jan. 5, 2016, U.S. ProvisionalPatent Application No. 62/275,199 filed Jan. 5, 2016, and U.S.Provisional Patent Application No. 62/275,711 filed Jan. 6, 2016. Theentire disclosure of each of these patent applications is incorporatedby reference herein.

BACKGROUND

The present invention relates generally to thermostats and moreparticularly to the improved control of a building or space's heating,ventilating, and air conditioning (HVAC) system through the use of amulti-function thermostat.

A thermostat is, in general, a component of an HVAC control system.Traditional thermostats sense the temperature of a system and controlcomponents of the HVAC in order to maintain a setpoint. A thermostat maybe designed to control a heating or cooling system or an airconditioner. Thermostats are manufactured in many ways, and use avariety of sensors to measure temperature and other desired parametersof a system.

Conventional thermostats are configured for one-way communication toconnected components, and to control HVAC systems by turning on or offcertain components or by regulating flow. Each thermostat may include atemperature sensor and a user interface. The user interface typicallyincludes a display for presenting information to a user and one or moreuser interface elements for receiving input from a user. To control thetemperature of a building or space, a user adjusts the setpoint via thethermostat's user interface.

SUMMARY

One implementation of the present disclosure is a multi-functionthermostat for a building. The thermostat includes a communicationinterface and a processing circuit. The communications interface isconfigured to communicate with an emergency server and receive occupanthealth data from one or more health sensors configured to monitor anoccupant of the building. The processing circuit is configured todetermine a health metric associated with the occupant based on theoccupant health data and cause the communications interface to send adistress message to the emergency server when the health metricassociated with the occupant indicates a medical emergency.

In some embodiments, the communications interface is configured tocommunicate with occupancy sensors. In some embodiments, n theprocessing circuit is configured to identify the occupant based onoccupancy data received from the occupancy sensors.

In some embodiments, at least one health sensors is a smart wrist bandand the occupant health data includes at least one of a heart rate and abody temperature.

In some embodiments, the processing circuit is configured to determinethe health metric associated with the occupant by identifying a measuredvalue indicated by the occupant health data. In some embodiments, themeasured value includes at least one of a body temperature of theoccupant, a heart rate of the occupant, and an insulin level of theoccupant, comparing the measured value to one or more stored thresholdvalues, and generating the health metric based on a result of thecomparing. In some embodiments, the health metric indicates whether themeasured value is above or below one or more of the stored thresholdvalues.

In some embodiments, the occupant health data includes a measured heartrate of the occupant. In some embodiments, the processing circuit isconfigured to determine the health metric associated with the occupantby monitoring the occupant health data for heart arrhythmia.

In some embodiments, the emergency server includes at least one of anemergency response operator server, a nurses' station computing system,and a hospital server. In some embodiments, the distress messageincludes a description of the medical emergency associated with theoccupant.

In some embodiments, the processing circuit is configured to push healthmessages to a user device. The health messages include at least one ofthe distress message, a reminder to take medication, and a reminder foran appointment.

In some embodiments, the communications interface is configured tocommunicate with a hospital server. In some embodiments, the processingcircuit is configured to push the occupant health data to the hospitalserver via the communications interface.

In some embodiments, the thermostat includes a user interface. In someembodiments, the processing circuit is configured to cause the userinterface to display information associated with the medical emergency,the information including at least one of a type of the medicalemergency, a name of the occupant in need of medical attention, and alocation of the occupant in the building.

Another implementation of the present disclosure is a method foroperating a multi-function thermostat for a building. The methodincludes receiving occupant health data from one or more health sensorsvia a communications interface of the thermostat. The method includesdetermining, by a processing circuit of the thermostat, a health metricassociated with an occupant of the building based on the occupant healthdata. The method includes causing the communications interface to send adistress message to an emergency server when the health metricassociated with the occupant indicates a medical emergency.

In some embodiments, the method further includes receiving occupancydata from one or more occupancy sensors via the communications interfaceand identifying the occupant based on occupancy data received from theoccupancy sensors.

In some embodiments, the health sensors include a smart wrist band andthe occupant health data includes at least one of a heart rate and abody temperature.

In some embodiments, the occupant health data includes a heart rate anddetermining the health metric includes monitoring the occupant healthdata for heart arrhythmia.

In some embodiments, the emergency server includes at least one of anemergency response operator server, a nurses' station computing system,and a hospital server, and the distress message includes a descriptionof the medical emergency associated with the occupant.

In some embodiments, the method further includes causing a userinterface to display medical emergency information including at leastone of the nature of a type medical emergency, a name of the occupant inneed of medical attention, and a location of the occupant in thebuilding.

In some embodiments, the method further includes causing thecommunications interface to push the occupant health data received fromthe heath sensors to a hospital server via the communications interface.

Another implementation of the present disclosure is a multi-functionthermostat for a building. The thermostat includes a communicationsinterface configured to communicate with an emergency server and receivehealth data from a wearable health sensor. The thermostat includes aprocessing circuit configured to determine a health metric associatedwith an individual wearing the wearable health sensor based on thehealth data received from the wearable health sensor. The processingcircuit is further configured to cause the communications interface tosend a distress message to the emergency server when the health metricassociated with the individual indicates a medical emergency.

In some embodiments, the wearable health sensor includes a smart wristband and the health data includes at least one of a heart rate and abody temperature.

In some embodiments, the processing circuit is configured to determinethe heath metric by monitoring the health data for heart arrhythmia whenthe health data includes a heart rate and monitoring the health data fortachycardia or bradycardia when the health data includes a heart rate.

In some embodiments, the wearable health sensor is an insulin pump andthe health data includes an insulin level of the individual. In someembodiments, the processing circuit is configured to compare themeasured insulin level to one or more stored threshold values andgenerate the health metric based on a result of the comparing. In someembodiments, the health metric indicates whether the measured value isabove or below one or more of the stored threshold values.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a HVAC system, accordingto an exemplary embodiment.

FIG. 2 is a drawing of multiple zones and floors of the building of FIG.1 equipped with control devices, according to an exemplary embodiment.

FIG. 3 is a block diagram of a waterside system that may be used inconjunction with the building of FIGS. 1-2, according to an exemplaryembodiment.

FIG. 4 is a block diagram of an airside system that may be used inconjunction with the building of FIGS. 1-2, according to an exemplaryembodiment.

FIG. 5 is a drawing of the connections of the control device of FIG. 2and FIG. 4, according to an exemplary embodiment.

FIG. 6 is a diagram of a communications system located in the buildingof FIGS. 1 and 2, according to an exemplary embodiment.

FIG. 7 is a block diagram illustrating the control device of FIGS. 2, 3,and 5 in greater detail, according to an exemplary embodiment.

FIG. 8 is a block diagram illustrating the control device of FIG. 7connected to three routers located in the building of FIGS. 1 and 2,according to an exemplary embodiment.

FIG. 9 is a flow diagram illustrating a process for determining thelocation of a mobile device in the building of FIG. 1 using theplurality of wireless emitters, according to an exemplary embodiment.

FIG. 10 is a drawing of a floorplan of a building with a main controlunit in one room and sensor units in other rooms, according to anexemplary embodiments.

FIG. 11 is a diagram illustrating the control device of FIG. 7 receivingoccupancy data, according to an exemplary embodiment.

FIG. 12 is a drawing of a building space and an occupant trackingapplication on the control device of FIG. 7, according to an exemplaryembodiment.

FIG. 13 is a flowchart of operations for controlling zones of a buildingwith the control device of FIG. 11, according to an exemplaryembodiment.

FIG. 14A is a flowchart of operations for controlling zones of abuilding with the control device of FIG. 11, according to an exemplaryembodiment.

FIG. 14B is a table of occupant permissions and preferences for thecontrol device of FIG. 7, according to an exemplary embodiment.

FIG. 15 is a diagram of the control device of FIG. 7 receiving emergencyand weather notifications, according to an exemplary embodiment.

FIG. 16A is a flowchart of operations for receiving emergencyinformation with the control device of FIG. 7, according to an exemplaryembodiment.

FIG. 16B is a flowchart of operations for prioritizing messages and datastreams with the control device of FIG. 7, according to an exemplaryembodiment.

FIG. 17 is a drawing of the control device of FIG. 15 displaying anemergency warning, according to an exemplary embodiment.

FIG. 18 is a drawing of the control device of FIG. 15 displaying anevacuation route, according to an exemplary embodiment.

FIG. 19 is a drawing illustrating the control device of FIG. 7 compilinga grocery list, according to an exemplary embodiment.

FIG. 20 is a flowchart of operations for compiling a grocery list withthe control device of FIG. 19, according to an exemplary embodiment.

FIG. 21 is a diagram of the control device of FIG. 7 communicating withhealth related devices and systems, according to an exemplaryembodiment.

FIG. 22 is a drawing of a medical application for the control device ofFIG. 21, according to an exemplary embodiment.

FIG. 23 is a drawing of another medical application for the controldevice of FIG. 21, according to an exemplary embodiment.

FIG. 24 is a diagram of the control device of FIG. 21 monitoring thehealth of an individual, according to an exemplary embodiment.

FIG. 25 is a drawing of a medical emergency screen displayed by thecontrol device of FIG. 21, according to an exemplary embodiment.

FIG. 26A is a diagram of the control device of FIG. 7 for hotel use,according to an exemplary embodiment.

FIG. 26B is a flow diagram of operations for scheduling hotelreservations with the control device of FIG. 7, according to anexemplary embodiment.

FIG. 27 is a flow diagram of operations for calling a taxi with thecontrol device of FIG. 7, according to an exemplary embodiment.

FIG. 28 is a set of drawings of screen displays for selecting roompreference of a hotel with the control device of FIG. 7, according to anexemplary embodiment.

FIG. 29 is a flow diagram of operations for preparing a hotel room foran occupant with the control device of FIG. 7, according to an exemplaryembodiment.

FIG. 30 is a flow diagram of operations for communicating with a frontdesk with the control device of FIG. 7, according to an exemplaryembodiment.

FIG. 31 is a flow diagram of operations for using a concierge feature ofthe control device of FIG. 7, according to an exemplary embodiment.

FIG. 32 is another flow diagram of operations for using a conciergefeature of the control device of FIG. 7, according to an exemplaryembodiment.

FIG. 33 is a flow diagram of operations for requesting hotelaccommodations with the control device of FIG. 7, according to anexemplary embodiment.

FIG. 34 is a flow diagram of operations for checking out of a hotel roomwith the control device of FIG. 7, according to an exemplary embodiment.

FIG. 35 is a block diagram illustrating the payment module of FIG. 7 ingreater detail, according to an exemplary embodiment.

FIG. 36 is a block diagram illustrating the input device of FIG. 7 ingreater detail, according to an exemplary embodiment.

FIG. 37 is a drawing illustrating the control device of FIG. 7 receivinga payment, according to an exemplary embodiment.

FIG. 38 is another drawing illustrating the control device of FIG. 7receiving a payment, according to an exemplary embodiment.

FIG. 39 is a flowchart of operations for processing a transaction withthe control device of FIG. 7, according to an exemplary embodiment.

DETAILED DESCRIPTION Overview

Referring generally to the FIGURES, a user control device is shown,according to various exemplary embodiments. The thermostat describedherein may be used in any HVAC system, room, environment, or systemwithin which it is desired to control and/or observe environmentalconditions (e.g., temperature, humidity, etc.). In traditional HVACsystems, a thermostat may be adjusted by a user to control thetemperature of a system.

The user control device is intended to provide the user with an abilityto function as a connected smart hub. The thermostat provides andesirable user interface for other environmental controls because of itsknown fixed location within a space. The user control device is intendedto be more personal, more efficient, and more aware than traditionalthermostats.

The user control device collects data about a space and the occupants ofthe space with various sensors (e.g., temperature sensors, humiditysensors, acoustic sensors, optical sensors, gas and other chemicalsensors, biometric sensors, motion sensors, etc.) and user inputs. Theuser control device may utilize data collected from a single room,multiple rooms, an entire building, or multiple buildings. The data maybe analyzed locally by the user control device or may be uploaded to aremote computing system and/or the cloud for further analysis andprocessing.

Building Management System and HVAC System

Referring now to FIGS. 1-4, an exemplary building management system(BMS) and HVAC system in which the systems and methods of the presentdisclosure may be implemented are shown, according to an exemplaryembodiment. Referring particularly to FIG. 1, a perspective view of abuilding 10 is shown. Building 10 is served by a BMS. A BMS is, ingeneral, a system of devices configured to control, monitor, and manageequipment in or around a building or building area. A BMS can include,for example, a HVAC system, a security system, a lighting system, a firealerting system, any other system that is capable of managing buildingfunctions or devices, or any combination thereof.

The BMS that serves building 10 includes an HVAC system 100. HVAC system100 may include a plurality of HVAC devices (e.g., heaters, chillers,air handling units, pumps, fans, thermal energy storage, etc.)configured to provide heating, cooling, ventilation, or other servicesfor building 10. For example, HVAC system 100 is shown to include awaterside system 120 and an airside system 130. Waterside system 120 mayprovide a heated or chilled fluid to an air handling unit of airsidesystem 130. Airside system 130 may use the heated or chilled fluid toheat or cool an airflow provided to building 10. An exemplary watersidesystem and airside system which may be used in HVAC system 100 aredescribed in greater detail with reference to FIGS. 2-3.

HVAC system 100 is shown to include a chiller 102, a boiler 104, and arooftop air handling unit (AHU) 106. Waterside system 120 may use boiler104 and chiller 102 to heat or cool a working fluid (e.g., water,glycol, etc.) and may circulate the working fluid to AHU 106. In variousembodiments, the HVAC devices of waterside system 120 may be located inor around building 10 (as shown in FIG. 1) or at an offsite locationsuch as a central plant (e.g., a chiller plant, a steam plant, a heatplant, etc.). The working fluid may be heated in boiler 104 or cooled inchiller 102, depending on whether heating or cooling is required inbuilding 10. Boiler 104 may add heat to the circulated fluid, forexample, by burning a combustible material (e.g., natural gas) or usingan electric heating element. Chiller 102 may place the circulated fluidin a heat exchange relationship with another fluid (e.g., a refrigerant)in a heat exchanger (e.g., an evaporator) to absorb heat from thecirculated fluid. The working fluid from chiller 102 and/or boiler 104may be transported to AHU 106 via piping 108.

AHU 106 may place the working fluid in a heat exchange relationship withan airflow passing through AHU 106 (e.g., via one or more stages ofcooling coils and/or heating coils). The airflow may be, for example,outside air, return air from within building 10, or a combination ofboth. AHU 106 may transfer heat between the airflow and the workingfluid to provide heating or cooling for the airflow. For example, AHU106 may include one or more fans or blowers configured to pass theairflow over or through a heat exchanger containing the working fluid.The working fluid may then return to chiller 102 or boiler 104 viapiping 110.

Airside system 130 may deliver the airflow supplied by AHU 106 (i.e.,the supply airflow) to building 10 via air supply ducts 112 and mayprovide return air from building 10 to AHU 106 via air return ducts 114.In some embodiments, airside system 130 includes multiple variable airvolume (VAV) units 116. For example, airside system 130 is shown toinclude a separate VAV unit 116 on each floor or zone of building 10.VAV units 116 may include dampers or other flow control elements thatcan be operated to control an amount of the supply airflow provided toindividual zones of building 10. In other embodiments, airside system130 delivers the supply airflow into one or more zones of building 10(e.g., via supply ducts 112) without using intermediate VAV units 116 orother flow control elements. AHU 106 may include various sensors (e.g.,temperature sensors, pressure sensors, etc.) configured to measureattributes of the supply airflow. AHU 106 may receive input from sensorslocated within AHU 106 and/or within the building zone and may adjustthe flow rate, temperature, or other attributes of the supply airflowthrough AHU 106 to achieve setpoint conditions for the building zone.

Referring now to FIG. 2, building 10 is shown in greater detail,according to an exemplary embodiment. Building 10 may have multiplezones. In FIG. 2, building 10 has zones, 202, 204, 206, 208, 210, and212. In building 10, the zones each correspond to a separate floor. Invarious embodiments, the zones of building 10 may be rooms, sections ofa floor, multiple floors, etc. Each zone may have a correspondingcontrol device 214. In some embodiments, control device 214 is at leastone of a thermostat, a sensor, a controller, a display device, aconcierge device, a medical monitor device, etc. Control device 214 maytake input from users. The input may be an environmental setpoint, aconcierge question, a payment, etc. In some embodiments, control device214 can cause music and/or building announcements to be played in one ormore of zones 202-212, cause the temperature and/or humidity to beregulated in one or more of zones 202-212, and/or any other controlaction.

In some embodiments, control device 214 can monitor the health of anoccupant 216 of building 10. In some embodiments, control device 214monitors heat signatures, heartrates, and any other information that canbe collected from cameras, medical devices, and/or any other healthrelated sensor. In some embodiments, building 10 has wirelesstransmitters 218 in each or some of zones 202-212. The wirelesstransmitters 218 may be routers, coordinators, and/or any other devicebroadcasting radio waves. In some embodiments, wireless transmitters 218form a Wi-Fi network, a Zigbee network, a Bluetooth network, and/or anyother kind of network.

In some embodiments, occupant 216 has a mobile device that cancommunicate with wireless transmitters 218. Control device 214 may usethe signal strengths between the mobile device of occupant 216 and thewireless transmitters 218 to determine what zone the occupant is in. Insome embodiments, control device 214 causes temperature setpoints, musicand/or other control actions to follow occupant 216 as the occupant 216moves from one zone to another zone (i.e., from one floor to anotherfloor).

In some embodiments, display devices 214 are connected to a buildingmanagement system, a weather server, and/or a building emergencysensor(s). In some embodiments, display devices 214 may receiveemergency notifications from the building management system, the weatherserver, and/or the building emergency sensor(s). Based on the nature ofthe emergency, display devices 214 may give directions to an occupant ofthe building. In some embodiments, the direction may be to respond to anemergency (e.g., call the police, hide and turn the lights off, etc.) Invarious embodiments, the directions given to the occupant (e.g.,occupant 216) may be navigation directions. For example, zone 212 may bea safe zone with no windows an individual (e.g., occupant 216). Ifdisplay devices 214 determines that there are high winds around building10, the control device 214 may direct occupants of zones 202-210 to zone212 if zone 212 has no windows.

Referring now to FIG. 3, a block diagram of a waterside system 300 isshown, according to an exemplary embodiment. In various embodiments,waterside system 300 may supplement or replace waterside system 120 inHVAC system 100 or may be implemented separate from HVAC system 100.When implemented in HVAC system 100, waterside system 300 may include asubset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller102, pumps, valves, etc.) and may operate to supply a heated or chilledfluid to AHU 106. The HVAC devices of waterside system 300 may belocated within building 10 (e.g., as components of waterside system 120)or at an offsite location such as a central plant.

In FIG. 3, waterside system 300 is shown as a central plant having aplurality of subplants 302-312. Subplants 302-312 are shown to include aheater subplant 302, a heat recovery chiller subplant 304, a chillersubplant 306, a cooling tower subplant 308, a hot thermal energy storage(TES) subplant 310, and a cold thermal energy storage (TES) subplant312. Subplants 302-312 consume resources (e.g., water, natural gas,electricity, etc.) from utilities to serve the thermal energy loads(e.g., hot water, cold water, heating, cooling, etc.) of a building orcampus. For example, heater subplant 302 may be configured to heat waterin a hot water loop 314 that circulates the hot water between heatersubplant 302 and building 10. Chiller subplant 306 may be configured tochill water in a cold water loop 316 that circulates the cold waterbetween chiller subplant 306 building 10. Heat recovery chiller subplant304 may be configured to transfer heat from cold water loop 316 to hotwater loop 314 to provide additional heating for the hot water andadditional cooling for the cold water. Condenser water loop 318 mayabsorb heat from the cold water in chiller subplant 306 and reject theabsorbed heat in cooling tower subplant 308 or transfer the absorbedheat to hot water loop 314. Hot TES subplant 310 and cold TES subplant312 may store hot and cold thermal energy, respectively, for subsequentuse.

Hot water loop 314 and cold water loop 316 may deliver the heated and/orchilled water to air handlers located on the rooftop of building 10(e.g., AHU 106) or to individual floors or zones of building 10 (e.g.,VAV units 116). The air handlers push air past heat exchangers (e.g.,heating coils or cooling coils) through which the water flows to provideheating or cooling for the air. The heated or cooled air may bedelivered to individual zones of building 10 to serve the thermal energyloads of building 10. The water then returns to subplants 302-312 toreceive further heating or cooling.

Although subplants 302-312 are shown and described as heating andcooling water for circulation to a building, it is understood that anyother type of working fluid (e.g., glycol, CO2, etc.) may be used inplace of or in addition to water to serve the thermal energy loads. Inother embodiments, subplants 302-312 may provide heating and/or coolingdirectly to the building or campus without requiring an intermediateheat transfer fluid. These and other variations to waterside system 300are within the teachings of the present disclosure.

Each of subplants 302-312 may include a variety of equipment configuredto facilitate the functions of the subplant. For example, heatersubplant 302 is shown to include a plurality of heating elements 320(e.g., boilers, electric heaters, etc.) configured to add heat to thehot water in hot water loop 314. Heater subplant 302 is also shown toinclude several pumps 322 and 324 configured to circulate the hot waterin hot water loop 314 and to control the flow rate of the hot waterthrough individual heating elements 320. Chiller subplant 306 is shownto include a plurality of chillers 332 configured to remove heat fromthe cold water in cold water loop 316. Chiller subplant 306 is alsoshown to include several pumps 334 and 336 configured to circulate thecold water in cold water loop 316 and to control the flow rate of thecold water through individual chillers 332.

Heat recovery chiller subplant 304 is shown to include a plurality ofheat recovery heat exchangers 326 (e.g., refrigeration circuits)configured to transfer heat from cold water loop 316 to hot water loop314. Heat recovery chiller subplant 304 is also shown to include severalpumps 328 and 330 configured to circulate the hot water and/or coldwater through heat recovery heat exchangers 326 and to control the flowrate of the water through individual heat recovery heat exchangers 226.Cooling tower subplant 208 is shown to include a plurality of coolingtowers 338 configured to remove heat from the condenser water incondenser water loop 318. Cooling tower subplant 308 is also shown toinclude several pumps 340 configured to circulate the condenser water incondenser water loop 318 and to control the flow rate of the condenserwater through individual cooling towers 338.

Hot TES subplant 310 is shown to include a hot TES tank 342 configuredto store the hot water for later use. Hot TES subplant 310 may alsoinclude one or more pumps or valves configured to control the flow rateof the hot water into or out of hot TES tank 342. Cold TES subplant 312is shown to include cold TES tanks 344 configured to store the coldwater for later use. Cold TES subplant 312 may also include one or morepumps or valves configured to control the flow rate of the cold waterinto or out of cold TES tanks 344.

In some embodiments, one or more of the pumps in waterside system 300(e.g., pumps 322, 324, 328, 330, 334, 336, and/or 340) or pipelines inwaterside system 300 include an isolation valve associated therewith.Isolation valves may be integrated with the pumps or positioned upstreamor downstream of the pumps to control the fluid flows in watersidesystem 300. In various embodiments, waterside system 300 may includemore, fewer, or different types of devices and/or subplants based on theparticular configuration of waterside system 300 and the types of loadsserved by waterside system 300.

Referring now to FIG. 4, airside system 400 is shown to include aneconomizer-type air handling unit (AHU) 402. Economizer-type AHUs varythe amount of outside air and return air used by the air handling unitfor heating or cooling. For example, AHU 402 may receive return air 404from building zone 406 via return air duct 408 and may deliver supplyair 410 to building zone 406 via supply air duct 612. In someembodiments, AHU 402 is a rooftop unit located on the roof of building10 (e.g., AHU 4506 as shown in FIG. 1) or otherwise positioned toreceive both return air 404 and outside air 414. AHU 402 may beconfigured to operate exhaust air damper 416, mixing damper 418, andoutside air damper 420 to control an amount of outside air 414 andreturn air 404 that combine to form supply air 410. Any return air 404that does not pass through mixing damper 418 may be exhausted from AHU402 through exhaust damper 416 as exhaust air 422.

Each of dampers 416-420 may be operated by an actuator. For example,exhaust air damper 416 may be operated by actuator 424, mixing damper418 may be operated by actuator 426, and outside air damper 420 may beoperated by actuator 428. Actuators 424-428 may communicate with an AHUcontroller 430 via a communications link 432. Actuators 424-428 mayreceive control signals from AHU controller 430 and may provide feedbacksignals to AHU controller 430. Feedback signals may include, forexample, an indication of a current actuator or damper position, anamount of torque or force exerted by the actuator, diagnosticinformation (e.g., results of diagnostic tests performed by actuators424-428), status information, commissioning information, configurationsettings, calibration data, and/or other types of information or datathat may be collected, stored, or used by actuators 424-428. AHUcontroller 430 may be an economizer controller configured to use one ormore control algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control actuators 424-428.

Still referring to FIG. 4, AHU 402 is shown to include a cooling coil434, a heating coil 436, and a fan 438 positioned within supply air duct612. Fan 438 may be configured to force supply air 410 through coolingcoil 434 and/or heating coil 436 and provide supply air 410 to buildingzone 406. AHU controller 430 may communicate with fan 438 viacommunications link 440 to control a flow rate of supply air 410. Insome embodiments, AHU controller 430 controls an amount of heating orcooling applied to supply air 410 by modulating a speed of fan 438.

Cooling coil 434 may receive a chilled fluid from waterside system 200(e.g., from cold water loop 316) via piping 442 and may return thechilled fluid to waterside system 200 via piping 444. Valve 446 may bepositioned along piping 442 or piping 444 to control a flow rate of thechilled fluid through cooling coil 474. In some embodiments, coolingcoil 434 includes multiple stages of cooling coils that can beindependently activated and deactivated (e.g., by AHU controller 430, byBMS controller 466, etc.) to modulate an amount of cooling applied tosupply air 410.

Heating coil 436 may receive a heated fluid from waterside system 200(e.g., from hot water loop 314) via piping 448 and may return the heatedfluid to waterside system 200 via piping 450. Valve 452 may bepositioned along piping 448 or piping 450 to control a flow rate of theheated fluid through heating coil 436. In some embodiments, heating coil436 includes multiple stages of heating coils that can be independentlyactivated and deactivated (e.g., by AHU controller 430, by BMScontroller 466, etc.) to modulate an amount of heating applied to supplyair 410.

Each of valves 446 and 452 may be controlled by an actuator. Forexample, valve 446 may be controlled by actuator 454 and valve 452 maybe controlled by actuator 456. Actuators 454-456 may communicate withAHU controller 430 via communications links 458-460. Actuators 454-456may receive control signals from AHU controller 430 and may providefeedback signals to controller 430. In some embodiments, AHU controller430 receives a measurement of the supply air temperature from atemperature sensor 462 positioned in supply air duct 612 (e.g.,downstream of cooling coil 434 and/or heating coil 436). AHU controller430 may also receive a measurement of the temperature of building zone406 from a temperature sensor 464 located in building zone 406.

In some embodiments, AHU controller 430 operates valves 446 and 452 viaactuators 454-456 to modulate an amount of heating or cooling providedto supply air 410 (e.g., to achieve a set point temperature for supplyair 410 or to maintain the temperature of supply air 410 within a setpoint temperature range). The positions of valves 446 and 452 affect theamount of heating or cooling provided to supply air 410 by cooling coil434 or heating coil 436 and may correlate with the amount of energyconsumed to achieve a desired supply air temperature. AHU 430 maycontrol the temperature of supply air 410 and/or building zone 406 byactivating or deactivating coils 434-436, adjusting a speed of fan 438,or a combination of both.

Still referring to FIG. 4, airside system 400 is shown to include abuilding management system (BMS) controller 466 and a control device214. BMS controller 466 may include one or more computer systems (e.g.,servers, supervisory controllers, subsystem controllers, etc.) thatserve as system level controllers, application or data servers, headnodes, or master controllers for airside system 400, waterside system200, HVAC system 100, and/or other controllable systems that servebuilding 10. BMS controller 466 may communicate with multiple downstreambuilding systems or subsystems (e.g., HVAC system 100, a securitysystem, a lighting system, waterside system 200, etc.) via acommunications link 470 according to like or disparate protocols (e.g.,LON, BACnet, etc.). In various embodiments, AHU controller 430 and BMScontroller 466 may be separate (as shown in FIG. 4) or integrated. In anintegrated implementation, AHU controller 430 may be a software moduleconfigured for execution by a processor of BMS controller 466.

In some embodiments, AHU controller 430 receives information from BMScontroller 466 (e.g., commands, set points, operating boundaries, etc.)and provides information to BMS controller 466 (e.g., temperaturemeasurements, valve or actuator positions, operating statuses,diagnostics, etc.). For example, AHU controller 430 may provide BMScontroller 466 with temperature measurements from temperature sensors462-464, equipment on/off states, equipment operating capacities, and/orany other information that can be used by BMS controller 466 to monitoror control a variable state or condition within building zone 406.

Control device 214 may include one or more of the user control devices.Control device 214 may include one or more human-machine interfaces orclient interfaces (e.g., graphical user interfaces, reportinginterfaces, text-based computer interfaces, client-facing web services,web servers that provide pages to web clients, etc.) for controlling,viewing, or otherwise interacting with HVAC system 100, its subsystems,and/or devices. Control device 214 may be a computer workstation, aclient terminal, a remote or local interface, or any other type of userinterface device. Control device 214 may be a stationary terminal or amobile device. For example, control device 214 may be a desktopcomputer, a computer server with a user interface, a laptop computer, atablet, a smartphone, a PDA, or any other type of mobile or non-mobiledevice. Control device 214 may communicate with BMS controller 466and/or AHU controller 430 via communications link 472.

Referring now to FIG. 5, control device 214 is shown as a connectedsmart hub or private area network (PAN), according to some embodiments.Control device 214 may include a variety of sensors and may beconfigured to communicate with a variety of external systems or devices.For example, control device 214 may include temperature sensors 502,speakers 504, leak detection system 508, health monitoring sensors 510,humidity sensors 514, occupancy sensors 516 a light detection sensors518, proximity sensor 520, a carbon dioxide sensors 522, or any of avariety of other sensors. Alternatively, control device 214 may receiveinput from external sensors configured to measure such variables. Theexternal sensors may not communicate over a PAN network but maycommunicate with control device 214 via an IP based network and/or theInternet.

In some embodiments, speakers 504 are located locally as a component ofcontrol device 214. Speakers 504 may be low power speakers used forplaying audio to the immediate occupant of control device 214 and/oroccupants of the zone in which control device 214 is located. In someembodiments, speakers 504 may be remote speakers connected to controldevice 214 via a network. In some embodiments, speakers 504 are abuilding audio system, an emergency alert system, and/or alarm systemconfigured to broadcast building wide and/or zone messages or alarms.

Control device 214 may communicate with a remote camera 506, a shadecontrol system 512, a leak detection system 508, a HVAC system, or anyof a variety of other external systems or devices which may be used in ahome automation system or a building automation system. Control device214 may provide a variety of monitoring and control interfaces to allowa user to control all of the systems and devices connected to controldevice 214. Exemplary user interfaces and features of control device 214are described in greater detail below.

Referring now to FIG. 6, a block diagram of communications system 600 isshown, according to an exemplary embodiment. System 600 can beimplemented in a building (e.g. building 10) and is shown to includecontrol device 214, network 602, healthcare sensor(s) 604, buildingemergency sensor(s) 606, weather server(s) 608, building managementsystem 610, and user device 612. System 600 connects devices, systems,and servers via network 602 so that building information, HVAC controls,emergency information, navigation directions, and other information canbe passed between devices (e.g., control device 214, user device 612,and/or building emergency sensor(s) 606 and servers and systems (e.g.,weather server(s) 608 and/or building management system 610). In someembodiments, control device 214 is connected to speakers 504 asdescribed with reference to FIG. 5.

In some embodiments, network 602 communicatively couples the devices,systems, and servers of system 600. In some embodiments, network 602 isat least one of and/or a combination of a Wi-Fi network, a wiredEthernet network, a Zigbee network, and a Bluetooth network. Network 602may be a local area network or a wide area network (e.g., the Internet,a building WAN, etc.) and may use a variety of communications protocols(e.g., BACnet, IP, LON, etc.) Network 602 may include routers, modems,and/or network switches.

In some embodiments, control device 214 is configured to receiveemergency information, navigation directions, occupant information,concierge information, and any other information via network 602. Insome embodiments, the information is received from building managementsystem 610 via network 602. In various embodiments, the information isreceived from the Internet via network 602. In some embodiments, controldevice 214 is at least one of or a combination of a thermostat, ahumidistat, a light controller, and any other wall mounted and/or handheld device. In some embodiments, control device 214 is connected tobuilding emergency sensor(s) 606. In some embodiments, buildingemergency sensor(s) 406 are sensors which detect building emergencies.Building emergency sensor(s) 406 may be smoke detectors, carbon monoxidedetectors, carbon dioxide detectors (e.g., carbon dioxide sensors 522),an emergency button (e.g., emergency pull handles, panic buttons, amanual fire alarm button and/or handle, etc.) and/or any other emergencysensor. In some embodiments, the emergency sensor(s) include actuators.The actuators may be building emergency sirens and/or building audiospeaker systems (e.g., speakers 504), automatic door and/or windowcontrol (e.g., shade control system 512), and any other actuator used ina building.

In some embodiments, control device 214 may be communicatively coupledto weather server(s) 608 via network 602. In some embodiments, thecontrol device 214 may be configured to receive weather alerts (e.g.,high and low daily temperature, five day forecast, thirty day forecast,etc.) from weather server(s) 608. Control device 214 may be configuredto receive emergency weather alerts (e.g., flood warnings, firewarnings, thunder storm warnings, winter storm warnings, etc.) In someembodiments, control device 214 may be configured to display emergencywarnings via a user interface of control device 214 when control device214 receives an emergency weather alert from weather server(s) 608. Thecontrol device 214 may be configured to display emergency warnings basedon the data received from building emergency sensor(s) 606. In someembodiments, the control device 214 may cause a siren (e.g., speakers504 and/or building emergency sensor(s) 606) to alert occupants of thebuilding of an emergency, cause all doors to become locked and/orunlocked, cause an advisory message be broadcast through the building,and control any other actuator or system necessary for responding to abuilding emergency.

In some embodiments, control device 214 is configured to communicatewith building management system 610 via network 602. Control device 214may be configured to transmit environmental setpoints (e.g., temperaturesetpoint, humidity setpoint, etc.) to building management system 610. Insome embodiments, building management system 610 may be configured tocause zones of a building (e.g., building 10) to be controlled to thesetpoint received from control device 214. In some embodiments, buildingmanagement system 610 may be configured to control the lighting of abuilding. In some embodiments, building management system 610 may beconfigured to transmit emergency information to control device 214. Insome embodiments, the emergency information is a notification of ashooter lockdown, a tornado warning, a flood warning, a thunderstormwarning, and/or any other warning. In some embodiments, buildingmanagement system 610 is connected to various weather servers or otherweb servers from which building management system 610 receives emergencywarning information. In various embodiments, building management systemis a computing system of a hotel. Building management system 610 maykeep track of hotel occupancy, may relay requests to hotel staff, and/orperform any other functions of a hotel computing system.

Control device 214 is configured to communicate with user device 612 vianetwork 602. In some embodiments, user device 612 is a smartphone, atablet, a laptop computer, and/or any other mobile and/or stationarycomputing device. In some embodiments, user device 612 communicatescalendar information to control device 214. In some embodiments, thecalendar information is stored and/or entered by a user into calendarapplication 614. In some embodiments, calendar application 414 is atleast one of Outlook, Google Calendar, Fantastical, Shifts, CloudCal,DigiCal, and/or any other calendar application. In some embodiments,control device 214 receives calendar information from the calendarapplication such as times and locations of appointments, times andlocations of meetings, and/or any other information. Control device 214may be configured to display building map direction to a user associatedwith user device 612 and/or any other information.

In some embodiments, a user may press a button on a user interface ofcontrol device 214 indicating a building emergency. The user may be ableto indicate the type of emergency (e.g., fire, flood, active shooter,etc.) Control device 214 may communicate an alert to building managementsystem 610, user device 612, and any other device, system, and/orserver.

In some embodiments, control device 214 is communicably coupled tohealthcare sensor(s) 604 via network 602. In some embodiments, controldevice is configured to monitor healthcare sensor(s) 604 collecting datafor occupants of a building (e.g., building 10) and determine healthmetrics for the occupants based on the data received from the healthcaresensor(s) 604. In some embodiments, healthcare sensor(s) 604 are one ormore smart wrist bands, pacemakers, insulin pumps, and/or any othermedical device. The health metrics may be determined based on heartrates, insulin levels, and/or any other biological and/or medical data.

Referring now to FIG. 7, a block diagram illustrating control device 214in greater detail is shown, according to some embodiments. Controldevice 214 is shown to include a variety of user interface devices 702and sensors 714. User interface devices 702 may be configured to receiveinput from a user and provide output to a user in various forms. Forexample, user interface devices 702 are shown to include electronicdisplay 706, an electronic display 706, ambient lighting 708, speakers710 (e.g., speakers 504), and input device 712. In some embodiments,user interface devices 702 include a microphone configured to receivevoice commands from a user, a keyboard or buttons, switches, dials, orany other user-operable input devices. It is contemplated that userinterface devices 702 may include any type of device configured toreceive input from a user and/or provide an output to a user in any of avariety of forms (e.g., touch, text, video, graphics, audio, vibration,etc.).

Sensors 714 may be configured to measure a variable state or conditionof the environment in which control device 214 is installed. Forexample, sensors 714 are shown to include a temperature sensor 716, ahumidity sensor 718, an air quality sensor 720, a proximity sensor 722,a camera 724, a microphone 726, a light sensor 728, and a vibrationsensor 730. Air quality sensor 720 may be configured to measure any of avariety of air quality variables such as oxygen level, carbon dioxidelevel, carbon monoxide level, allergens, pollutants, smoke, etc.Proximity sensor 722 may include one or more sensors configured todetect the presence of people or devices proximate to control device214. For example, proximity sensor 722 may include a near-fieldcommunications (NFC) sensor, a radio frequency identification (RFID)sensor, a Bluetooth sensor, a capacitive proximity sensor, a biometricsensor, or any other sensor configured to detect the presence of aperson or device. Camera 724 may include a visible light camera, amotion detector camera, an infrared camera, an ultraviolet camera, anoptical sensor, or any other type of camera. Light sensor 728 may beconfigured to measure ambient light levels. Vibration sensor 730 may beconfigured to measure vibrations from earthquakes or other seismicactivity at the location of control device 214.

Still referring to FIG. 7, control device 214 is shown to include acommunications interface 732 and a processing circuit 734.Communications interface 732 may include wired or wireless interfaces(e.g., jacks, antennas, transmitters, receivers, transceivers, wireterminals, etc.) for conducting data communications with varioussystems, devices, or networks. For example, communications interface 732may include an Ethernet card and port for sending and receiving data viaan Ethernet-based communications network and/or a Wi-Fi transceiver forcommunicating via a wireless communications network. Communicationsinterface 732 may be configured to communicate via local area networksor wide area networks (e.g., the Internet, a building WAN, etc.) and mayuse a variety of communications protocols (e.g., BACnet, IP, LON, etc.).

Communications interface 732 may include a network interface configuredto facilitate electronic data communications between control device 214and various external systems or devices (e.g., network 602, buildingmanagement system 610, HVAC equipment 738, user device 612, etc.) Forexample, control device 214 may receive information from buildingmanagement system 610 or HVAC equipment 738 indicating one or moremeasured states of the controlled building (e.g., temperature, humidity,electric loads, etc.) and one or more states of the HVAC equipment 738(e.g., equipment status, power consumption, equipment availability,etc.). In some embodiments, HVAC equipment 738 may be lighting systems,building systems, actuators, chillers, heaters, and/or any otherbuilding equipment and/or system. Communications interface 732 mayreceive inputs from building management system 610 or HVAC equipment 738and may provide operating parameters (e.g., on/off decisions, setpoints, etc.) to building management system 610 or HVAC equipment 738.The operating parameters may cause building management system 610 toactivate, deactivate, or adjust a set point for various types of homeequipment or building equipment in communication with control device214.

Processing circuit 734 is shown to include a processor 740 and memory742. Processor 740 may be a general purpose or specific purposeprocessor, an application specific integrated circuit (ASIC), one ormore field programmable gate arrays (FPGAs), a group of processingcomponents, or other suitable processing components. Processor 740 maybe configured to execute computer code or instructions stored in memory742 or received from other computer readable media (e.g., CDROM, networkstorage, a remote server, etc.).

Memory 742 may include one or more devices (e.g., memory units, memorydevices, storage devices, etc.) for storing data and/or computer codefor completing and/or facilitating the various processes described inthe present disclosure. Memory 742 may include random access memory(RAM), read-only memory (ROM), hard drive storage, temporary storage,non-volatile memory, flash memory, optical memory, or any other suitablememory for storing software objects and/or computer instructions. Memory742 may include database components, object code components, scriptcomponents, or any other type of information structure for supportingthe various activities and information structures described in thepresent disclosure. Memory 742 may be communicably connected toprocessor 740 via processing circuit 734 and may include computer codefor executing (e.g., by processor 740) one or more processes describedherein. For example, memory 742 is shown to include a voice commandmodule 744, a building module 746, a voice control module 748, a paymentmodule 758, a hotel module 750, a healthcare module 752, an occupancymodule 754, and an emergency module 756. The functions of some of thesemodules is described in greater detail below.

In some embodiments, voice command module 744 is configured to receiveaudio data from microphone 726. Voice command module 744 may configuredto translate audio data into spoken words. In some embodiments, voicecommand module 744 may be configured to perform Internet searches basedon the spoken words via network 602. In various embodiments, voicecommand module 744 may send requests to building management system 610based on the spoken words.

Occupancy Tracking Features

Referring now to FIG. 8, a block diagram of an occupancy tracking system800 is shown according to an exemplary embodiment. System 800 can beimplemented in a building space (e.g., building 10) to determine theoccupancy of the building space based on Wi-Fi router connections andsignal strengths. System 800 is shown to include building managementsystem 610, control device 214, network 602, routers 804-808, and userdevice 612. In some embodiments, building management system 610 operatesthe building space as described in FIGS. 1-4. In various embodiments,control device 214 operates the building space as described in FIGS.1-4. Building management system 610 is shown to be connected to controldevice 214 and routers 804-808. In some embodiments, network 602 is atleast one of and/or a combination of a Wi-Fi network, a wired Ethernetnetwork, a Zigbee network, and a Bluetooth network. Network 602 may be alocal area network or a wide area network (e.g., the Internet, abuilding WAN, etc.) and may use a variety of communications protocols(e.g., BACnet, IP, LON, etc.).

Building management system 610 may include an application server. Theapplication server may be a remote server and may be hosted at a remotelocation. The application server may be configured to provide aweb-based presence for users and/or building administrators to accessinformation regarding occupancy of the building. In some embodiments,the application server allows users and/or building administrators toview data pertaining to the number of users in the building space andtheir respective locations. The application server may communicate withuser device 612 through routers 804-808 or may communicate to userdevice 612 via mobile data (e.g. 1G, 2G, 3G, LTE, etc.).

In some embodiments, the application server integrates a buildingfacility web application with the determined number and location ofoccupants. In some embodiments, the building facility application maycontrol room, zone, building, and campus lighting, booking, publicservice announcements and other features of a building facility. In someembodiments, the building facility web application may identify a userwhen a device associated with the user (e.g., user device 612) isdetected in a room, zone, building and/or campus based on wirelesssignal strengths. The building facility web application mayautomatically login the identified user with the building web facilityapplication. A user that has been logged in may be able to changelighting, environmental setpoints and any other adjustable buildingfacility web application feature via user device 612. In someembodiments, the building facility web application may automaticallyadjust lighting and environmental setpoints to preferred settings of theidentified and logged in user.

Routers 804-808 may be installed for the specific purpose of determininguser occupancy or may be existing routers in a wireless buildingnetwork. In some embodiments, each router may have a unique ID. In FIG.8, router 804 has the ID B1, router 806 has the ID A1, and router 808has the ID C1. Routers 804-808 may connect user device 612 to theInternet and/or control device 214 through network 602. Although onlythree routers 804-808 are shown in FIG. 8, it is contemplated thatsystem 800 can include any number of routers located in the buildingspace.

Routers 804-808 can be configured to emit, receive, sense, relay, orotherwise engage in unidirectional or bidirectional wirelesscommunications. Routers 804-808 can use any type wireless technology orcommunications protocol. For example, in various embodiments, thewireless emitters/receivers can be Bluetooth low energy (BLE) emitters,near field communications (NFC) devices, Wi-Fi transceivers, RFIDdevices, ultrawide band (UWB) devices, infrared emitters/sensors,visible light communications (VLC) devices, ultrasound devices, cellulartransceivers, iBeacons, or any other type of hardware configured tofacilitate wireless data communications. In some embodiments, routers804-808 are integrated with various devices within the building (e.g.,thermostats, lighting sensors, zone controllers).

Routers 804-808 can broadcast a wireless signal. The wireless signalbroadcast by routers 804-808 can include the identifier associated withrouters 804-808. For example, routers 804-808 can broadcast a SSID, MACaddress, or other identifier which can be used to identify a particularrouter. In some embodiments, the wireless signal broadcast by routers804-808 includes multiple emitter identifiers (e.g., a UUID value, amajor value, a minor value, etc.). User device 612 can detect thewireless signals emitted by the routers 804-808. User device 612 can beconfigured to identify the router associated with the wireless signal.In some embodiments, user device 612 detects the signal strength of thewireless signals for each of routers 804-808.

In FIG. 8, user device 612 communicates with routers 804-808. Userdevice 612 may communicate to the routers via Wi-Fi, Zigbee, Bluetooth,and/or any other wireless communication protocol. User device 612 maycommunicate to routers 804-808 and determine a signal strength of eachrouter. In some embodiments, received signal strength (RSSI) isdetermined by user device 612 for connections to each of routers804-808. In some embodiments, user device 612 detects the RSSI of thewireless signals received from each of routers 804-808 without engagingin bidirectional communications with any of routers 804-808. Forexample, user device 612 can passively detect or measure RSSI withoutactively sending any return data to routers 804-808. In variousembodiments, user device 612 determines RSSI as a percentage, in mW, indBm, and/or in any other unit or power ratio.

User device 612 may store the location of each router 804-808 in amemory device and may determine (e.g., triangulate, estimate, etc.) thelocation of user device 612 based on the stored locations of routers804-808 and the determined RSSI value for each router. In someembodiments, user device 612 is only connected to a single router oronly receives a wireless signal from a single router. User device 612may determine an approximate circular field around the single router inwhich user device 612 may be located based on the determined RSSI. Insome embodiments, the circular field is an approximate radius such as adistance that user device 612 may be located away from the router. Forexample, a strong RSSI may indicate that user device 612 is close to aparticular router, whereas a weaker RSSI may indicate that user device612 is further from the router. User device 612 can use a mapping tableor function to translate RSSI into distance. In some embodiments, thetranslation between RSSI and distance is a function of the router'sbroadcast power or other router settings, which user device 612 canreceive from each router within broadcast range. In some embodiments,the field is a range of radii. Each radii may be different and userdevice 612 may be located between the two radii in a disc shaped field.In various embodiments, user device 612 triangulates the location ofuser device 612 based on one or more signal strengths between knownlocations of routers.

In various embodiments, routers 804-808 send signal strengths betweenrouters 804-808 and user device 612 to control device 214. Controldevice 214 may store the location of each router 804-808 in a memorydevice and may determine (e.g., triangulate, estimate, etc.) thelocation of user device 612 based on the stored locations of routers804-808 and the determined RSSI value for each router. In someembodiments, user device 612 is only connected to a single router oronly receives a wireless signal from a single router. Control device 214may determine an approximate circular field around the single router inwhich user device 612 may be located based on the determined RSSI. Insome embodiments, the circular field is an approximate radius such as adistance that user device 612 may be located away from the router. Forexample, a strong RSSI may indicate that user device 612 is close to aparticular router, whereas a weaker RSSI may indicate that user device612 is further from the router. Control device 214 can use a mappingtable or function to translate RSSI into distance. In some embodiments,the translation between RSSI and distance is a function of the router'sbroadcast power or other router settings, which control device 214 canreceive from each router within broadcast range. In some embodiments,the field is a range of radii. Each radii may be different and userdevice 612 may be located between the two radii in a disc shaped field.In various embodiments, control device 214 triangulates the location ofuser device 612 based on one or more signal strengths between knownlocations of routers.

Still referring to FIG. 8, user device 612 may communicate with buildingmanagement system 610, an application server, and/or control device 214via the routers 804-808. In some embodiments, user device 612 sends itslocation within the building space to building management system 610, anapplication server, and/or control device 214. In some embodiments, userdevice 612 sends a unique ID to building management system 610 and/or anapplication server. In FIG. 8, the unique ID of user device 612 is PhoneA. In some embodiments, building management system 610 is configured torun a unique heating or cooling schedule based on the ID of the userdevice 612. For example, an environmental setpoint may be tied to the IDof user device 612. Building management system 610 may be configured toadjust the setpoint of the zone in which user device 612 is located tothe environmental setpoint tied to the ID of user device 612.

Referring now to FIG. 9, a flow diagram illustrating a process 900 forusing occupant location in a building is shown, according to anexemplary embodiment. A building (e.g., building 10) is equipped with aplurality of wireless emitters 902. Each of wireless emitters 902 may belocated at a different position in the building and may be associatedwith a different emitter identifier. Although only one wireless emitter902 is shown in FIG. 9, many wireless emitters 902 may be placed atvarious locations in or around the building. Each of wireless emitters902 broadcasts a wireless signal (step 904). The wireless signalbroadcast by emitter 902 includes an indication of an emitter identifierassociated with wireless emitter 902. In some embodiments, the wirelesssignal broadcast by emitter 902 include multiple emitter identifiers(e.g., a UUID value, a major value, a minor value, etc.)

Still referring to FIG. 9, a user device 612 detects the wireless signalemitted by wireless emitter 902 (step 906). User device 612 may be, forexample, a laptop computer, a tablet, a smart phone, a RFID sensor, aBluetooth device, a Wi-Fi device, a NFC device, a portablecommunications device, or any combination thereof. User device 612 maybe configured to run remote applications 908 and may function as a UIclient. User device 612 may be configured (e.g., by an applicationrunning on user device 612) to identify the emitter identifierassociated with the wireless signal detected in step 906.

In FIG. 9, user device 612 is shown connecting to an application gateway910 (e.g., at a predefined IP address, via a wireless data connection)and reporting the emitter identifier associated with the detectedwireless signal (step 912). In some embodiments, user device 612requests a user interface for presentation on user device 612. Therequest may include the emitter identifier detected by user device 612and/or a device identifier associated with user device 612. Applicationgateway 910 may provide the emitter identifier and/or the deviceidentifier to building management system 610. In various embodiments,application gateway 910 and building management system 610 may becombined into a single component or user device 612 may report theemitter identifier directly to building management system 610.

Building management system 610 uses the emitter identifier and/or thedevice identifier to select a user interface for presentation on userdevice 612. Building management system 610 may select the user interfacefor a building zone associated with the emitter identifier reported byuser device 612. For example, building management system 610 may selecta user interface which includes information and/or control optionsrelating to the building zone associated with the reported emitteridentifier. In some embodiments, building management system 610 selectsa user interface based on the identity of a user associated with userdevice 612 (e.g., based on a user identifier or device identifierreported by user device 612). In some embodiments, building managementsystem 610 uses emitter identifier reported by user device 612 todetermine the position of user device 612 within the building. Buildingmanagement system 610 may send the position of user device 612 tocontrol device 214. Building management system 610 may select a userinterface for monitoring and/or controlling the building zone in whichuser device 612 is currently located or a building zone in which userdevice 612 has been located previously.

Still referring to FIG. 9, building management system 610 is shownproviding the selected user interface to application gateway 910 (step914), which provides the selected user interface to user device 612(step 916). In other embodiments, BMS controller 12 may provide theselected user interface directly to user device 612. User device 612 maypresent the selected user interface on a user interface of user device612. The use interface may be, for example, an electronic display orother user interface element of user device 612. Advantageously,building management system 610 may automatically detect the location ofuser device 612 and deliver a location-specific user interface to userdevice 612 without requiring a user to input location information.

Referring now to FIG. 10, a floorplan 1000 of a home and/or building isshown. The home is shown to include several different zones (e.g., roomsor areas) including a living room, a first bedroom, a second bedroom, abathroom, a kitchen, and a dining room. A control device 214 may beinstalled in one of the rooms or zones. For example, FIG. 10 shows amain control unit (e.g., control device 214) installed in the livingroom. The main control unit may serve as a central hub for monitoringenvironmental conditions, controlling various devices throughout thehome, and/or tracking occupancy through multiple rooms and/or zones ofthe home.

Sensor units 1002 (e.g., proximity sensor 520, remote camera 506,occupancy sensor 516, routers 804-808, emitter 902, etc.) may beinstalled in various rooms or zones in the home. For example, FIG. 10shows a sensor unit installed in each of the bedrooms, the bathroom, thekitchen, and the dining room. In some embodiments, the sensors 1002measure signals strengths between user devices (e.g., user device 612).In various embodiments, sensors 1002 are configured to relay image dataand/or audio data to control device 214. Control device 214 may identifyoccupants based on the image and/or audio data. The measured signalstrengths may be used to determine the occupancy of the owner of theuser device.

In some embodiments, a building management system and/or control device214 determines the location of the user device. The sensor units 1002may be configured to measure environmental conditions within each roomor zone and to receive user input (e.g., voice commands via amicrophone). For example, each sensor unit 1002 may include a pluralityof sensors (e.g., a temperature sensor, a humidity sensor, a smokedetector, a light sensor, a camera, a motion sensor etc.) configured tomeasure variables such as temperature, humidity, light, etc. in the roomor zone in which the sensor unit is installed. The sensor units 1002 maycommunicate (e.g., wirelessly or via a wired communications link) withthe control device 214 and/or with each other. In some embodiments,sensors, such as low power door sensors, can communicate with repeatersdisposed in the gang boxes or other locations using a low power overheadprotocol. The repeaters can provide wired or wireless communication tothe main control unit.

Referring now to FIG. 11, a diagram of control device 214 receivingoccupancy information is shown, according to an exemplary embodiment. Insome embodiments, control device 214 is configured to receive occupancydata 1102 from sensors 714. In some embodiments, sensors 714 are atleast one or a combination of camera 724, microphone 726, a motionsensor (e.g., proximity 722), and/or any other occupancy sensor. In someembodiments, occupancy module 754 may be configured to process theoccupancy data to determine the identity of any detected occupants.

In some embodiments, occupancy module 754 may be configured to determinethe identity of an occupant based on occupancy data 1102 received fromsensors 714. In some embodiments, the occupancy module 754 receivessensor input from sensors 714 where the sensors may include camera 724.Occupancy module 754 can perform digital image processing to identifythe one or more users based on the digital images received from camera724. In some embodiments, digital image processing is used to identifythe faces of the one or more users, the height of the one or more users,or any other physical characteristic of the one or more users. In someembodiments, the digital image processing is performed by image analysistools such as edge detectors and neural networks. In some embodiments,the digital image processing compares the physical characteristics ofthe one or more users with physical characteristics of previouslyidentified users.

In some embodiments, the occupancy module 754 receives sensor input frommicrophone 726. Microphone 726 can be any of a plurality of microphonetypes. The microphone types include, for example, a dynamic microphone,a ribbon microphone, a carbon microphone, a piezoelectric microphone, afiber optic microphone, a laser microphone, a liquid microphone, and anaudio speaker used as a microphone. In some embodiments, the occupancycontroller analyzes the audio data received from the microphone. In someembodiments, the occupancy controller 636 identifies one or more usersbased on voice biometrics of the audio received from microphone 726.Voice biometrics are the unique characteristics of a speaker's voice.Voice biometrics include voice pitch or speaking style that result fromthe anatomy of the speaker's throat and/or mouth. In some embodiments,the occupancy module 754 uses a text dependent voice recognitiontechnique. In some embodiments, the occupancy module 754 uses a textindependent voice recognition technique to identify the one or moreusers. Occupancy module 754 may be configured to store voice biometricslinked to individuals. Occupancy module 754 may be configured to matchthe stored voice biometrics to voice biometrics determined foroccupants.

In some embodiments, the occupancy module 754 uses the text dependentvoice recognition technique to identify the one or more users based on apassword or particular phrase spoken by one of the users. For example,the user may speak a phrase such as “This is Felix, I am home.” Theoccupancy module 754 can perform speech recognition to determine thespoken phrase “This is Felix, I am home” from the audio data receivedform the microphone. In some embodiments, occupancy module 754 uses oneor a combination of a hidden Markov models, dynamic time warping, and aneural networks to determine the spoken phrase. Occupancy module 754compares the determined spoken phrase to phrases linked to users. If thephrase, “This is Felix, I am home” matches a phrase linked to a userFelix, the occupancy controller identifies the user as Felix.

In some embodiments, occupancy module 754 uses the text independentvoice recognition technique to identify one or more users based onparticular voice biometrics of the user. The text independent voicerecognition technique performs a pattern recognition technique toidentify the particular voice biometrics of the speaker from the audiodata received from the microphone. The voice biometrics include voicepitch and speaking style. In some embodiments, a plurality of techniquesare used to identify the voice biometrics of the user. The techniquesinclude frequency estimation, hidden Markov models, Gaussian mixturemodels, pattern matching algorithms, neural networks, matrixrepresentation, Vector Quantization, and decision trees.

In some embodiments, the occupancy module 754 is configured to captureaudio data from one or more users and perform pre-processing. In someembodiments pre-processing may be compressing the audio data, convertingthe audio data into an appropriate format, and any other pre-processingaction necessary. The occupancy module 754 may be configured to transmitthe captured spoken audio data to a voice recognition server viacommunications interface 732 and network 602 as described with referenceto FIGS. 6-7. The voice recognition server (e.g., building managementsystem 610) may be configured to determine the identity of the occupantand transmit the identity of the occupant to occupancy module 754.

Still referring to FIG. 11, control device 214 is configured to receiveoccupancy information 1104 from building management system 610. In someembodiments, building management system 610 may be configured todetermine the location of a user based on trilateration methods asdescribed with reference to FIG. 8. In various embodiments, buildingmanagement system 610 may be configured to determine the location of auser based on signal strength to an emitter as described with referenceto FIG. 9.

The building management system 610 may send the identity of the occupantand the location of the occupant in a building (e.g., building 10). Insome embodiments, control device 214 is configured to cause zones and/orbuildings to be controlled to environmental conditions (e.g.,temperature setpoint, humidity setpoint, etc.) based on environmentalcondition preferences and location of the occupant. The control device214 may be configured to generate control signals for HVAC equipment 738to achieve the preferred environmental conditions. In variousembodiments, the control device 214 may be configured to play music indifferent zones and/or cause a music platform (e.g., Pandora, Spotify,etc.) to play music preferences of the identified user in the zoneand/or building which the user is located.

Referring now to FIGS. 12-13, a diagram 1200 and flowchart 1300illustrating a process for controlling a building zone based on detectedoccupancy is shown, according to an exemplary embodiment. In someembodiments, the process is performed by occupancy module 754, asdescribed with reference to FIG. 7. Control device 214 may identify auser and load user-specific climate control settings for the identifieduser (step 1302). In some embodiments, control device 214 identifies theuser by communicating with a portable device carried by the user (e.g.,a phone, a RFID card, a NFC tag, etc.) In other embodiments, the user isidentified by voice (FIG. 11), by appearance (FIG. 11), trilateration ofwireless signals from a user device (FIG. 8), communicating withwireless emitters via a user device (FIG. 9) or any other data collectedby sensors in zones 1202 and 1204. Control device 214 may determine thatthe user is located within a first zone 1202 of a home or building (step1304) and may operate home/building equipment to achieve theuser-specific climate control settings in the first zone 1202 (step1306). Control device 214 may turn the lights on in zone 1202 (step1308). In some embodiments, the lights are dimmed to user specifiedlevels. Control device 214 may be configured to operating music playedin zones 1202 when the user is identified (step 1310). In someembodiments, the user is linked to specific songs, playlists, and/orvolumes. Control device 214 may be configured to cause audio systems toplay certain playlists and/or radios in zone 1202 when the user isidentified in zone 1202.

Control device 214 may determine that the user has moved to a secondzone 1204 of the home/building (step 1308) and may operate thehome/building equipment to achieve the user-specific climate controlsettings in the second zone 1204 (step 1310). In some embodiments,control device 214 is configured to operate the lighting of zones 1202and 1204 based upon the location of the user (step 1312). For example,control device 214 may turn off lights in zone 1202 and on in zone 1204when the user moves from zone 1202 to zone 1204 (step 1316). Controldevice 214 may be configured to operating music played in zones 1202 and1204 when the user moves from zone 1202 to 1204 (step 1316). Forexample, when the user moves to zone 1204, the music may stop playing inzone 1202 and being playing in 1204 (step 1318).

Referring now to FIG. 14A, a flowchart 1400 illustrating a buildingcontrol process which may be performed by occupancy module 754 ofcontrol device 214 as described with reference to FIG. 7, according toan exemplary embodiments. In some embodiments, control device 214 isconfigured to determine the location and identity of a user based onwireless communication (step 1402) with user device 612 when user device612 is associated with the user. In some embodiments, wirelesstriangulation is used to determine the location of the user based onsignal strengths between user device 612 and routers and/or emitters asdescribed with reference to FIGS. 8-9.

In some embodiments, a unique device identifier (e.g., a serial number,a hardware ID, a MAC address, etc.) may link user device 612 to aparticular user profile. When user device 612 is determined to be in thebuilding (e.g., building 10) the user may receive a command toauthenticate (i.e., log in) with building management system 610 via userdevice 612 (step 1404). In some embodiments, user device 612automatically authenticated with the building management system 610based on a unique device identifier. In some embodiments, theauthentication is performed directly between the user device and thebuilding management system 610. In various embodiments, control device214 receives the unique device identifier from the user device andfacilitates the authentication with building management system 610. Invarious embodiments, the user may be prompted to enter a user name andpassword via user device 612 and/or user interface 702 of display device214 to authenticate with the building management system 610.

In some embodiments, the building management system 610 may beconfigured to generate a three dimensional building map with thelocation and identity of multiple building occupants located on the map(step 1406). The building map may contain multiple floors, zones,buildings, and/or campuses. In some embodiments, the three dimensionalbuilding map may be accessible via a user device (e.g., user device 612)if the user device has the proper permissions to view the building map.In some embodiments, the user device must be associated with atechnician, and/or any other building employee for the user to haveaccess to the three dimensional building map.

In some embodiments, building management system 610 keeps a record ofvarious occupants of the building and associated permissions with eachoccupant. In some embodiments, the permissions are music permission(i.e., if the user can change music, radio stations, volume, etc. of themusic played in various zones of the building). In some embodiments, thepermissions allow a user to change music, radio stations, music volume,environmental setpoints, lighting and/or any other adjustable setting ofcontrol device 214 via user interface 702, microphone 726, and/or userdevice 612 associated with the user. In some embodiments, thepermissions to change and/or adjust environmental conditions (e.g.,temperature setpoint, humidity setpoint, etc.) (step 1408). Based on thepermissions and user preferences, the building management system 610 maybe configured to send commands to the devices (e.g., control device 214)to adjust environmental zone conditions, lighting, and music of zones(step 1410).

Referring now to FIG. 14B, table 1412 of occupant permissions andpreferences is shown, according to an exemplary embodiment. In someembodiments, the table may be permissions and preferences which controldevice 214 receives from building management system 610 as describedwith reference to FIG. 11 and/or FIG. 14A. In some embodiments, table412 contains permissions and preferences for occupant A 1414, occupant B1416, and occupant C 1418. Permissions and preferences for any number ofoccupants may be received from building management system 610 and/orstored on control device 214. Occupant A 1414, occupant B 1416, andoccupant C 1418 may have preferred preferences such as preferredsetpoint 1420, music 1422, lighting 1424, and shades/blinds 1426.Occupant A 1414, occupant B 1416, and occupant C 1418 may havepermissions to change and/or operate certain features of control device214 (i.e., setpoints, music, lighting, etc.) Any number of permissionsand/or preferences may be received from building management system 610for occupant A 1414, occupant B 1416, and occupant C 1418.

Occupant A 1414 has a preferred setpoint of 78 degrees F., occupant B1416 has a preferred setpoint of 75 degrees F. and occupant C 1418 hasno permission to change the setpoint. In some embodiments, when anoccupant with a preferred setpoint moves from a first zone to a secondzone, the preferred setpoint may follow the occupant and the second zonemay be heated and/or cooled to the preferred setpoint. An occupant withno permission to change a setpoint (e.g., occupant C 1418) may not beable to make any changes to the setpoint.

In some embodiments, control device 214 may disable changes to thesetpoint whenever occupant C 1418 is determined to be a set distancesfrom control device 214. In some embodiments, control device 214 maydisable changes to the lighting whenever occupant C 1418 is identifiedin the zone that control device 214 is located. In some embodiments,when occupant C 1418 is authenticated and/or logged in with the buildingmanagement system and/or control device 214 as described with referenceto FIG. 14A, occupant C 1418 may be notified via a user device (e.g.,user device 612) that occupant C 1418 is unable to change the setpoint.In some embodiments, occupant C 1418 is notified via the user interface702 (e.g., through images on electronic display 706, audio from speakers710, etc.) that occupant C 1418 does not have permission to adjust thesetpoint.

Occupant A 1414, occupant B 1416, and occupant C 1418 may havepermissions and preferences for music 1422 such as the music played inzones of a building (e.g., building 10). In table 1412, occupant A 1414has a preference for no music, occupant B 1416 has a preferred radiostation, and occupant C 1418 does not have permission to play music. Insome embodiments, whenever occupant B 1416 is in a zone, the buildingequipment in that zone may automatically play radio station AM 1130. Insome embodiments, when occupant A 1414 enters a zone, the buildingequipment in that zone will automatically turn off any music that isplaying. In some embodiments, any attempt by occupant C 1418 to playmusic and/or audio will be met by a notification that occupant C 1418does not have the appropriate permissions to change the music and/oraudio.

In some embodiments, control device 214 may disable changes to musicpreferences whenever occupant C 1418 is determined to be a set distancesfrom control device 214. In some embodiments, control device 214 maydisable changes to the lighting whenever occupant C 1418 is identifiedin the zone that control device 214 is located. In some embodiments,when occupant C 1418 is authenticated and/or logged in with buildingmanagement system 610 and/or control device 214 via a user device (e.g.,user device 612) as described with reference to FIG. 14B, occupant C1418 may be notified via a user device (e.g., user device 612) thatoccupant C 1418 is unable to change the music preferences. In someembodiments, occupant C 1418 is notified via the user interface 702(e.g., through images on electronic display 706, audio from speakers710, etc.) that occupant C 1418 does not have permission to adjust themusic preferences.

Occupant A 1414, occupant B 1416, and occupant C 1418 may havepermissions and preferences for lighting 1424. In some embodiments, thelighting in zones and/or a building (e.g., building 10) may be adjustedbased on permissions and preferences of occupant A 1414, occupant B1416, and occupant C 1418. Occupant A 1414 may have no permission tochange lighting. Occupant B 1416 may have a preference for lighting inthe zone which occupant B occupies to be dim. Occupant C 1418 may havethe preference that the lighting associated with the zone which occupantC 1418 occupies be at full brightness.

In some embodiments, control device 214 may disable changes to thelighting whenever occupant A 1414 is determined to be a set distancesfrom control device 214. In some embodiments, control device 214 maydisable changes to the lighting whenever occupant A 1414 is identifiedin the zone that control device 214 is located. In some embodiments,when occupant A 1414 is authenticated and/or logged in with buildingmanagement system 610 and/or control device 214 via a user device (e.g.,user device 612) as described with reference to FIG. 14A, occupant A1414 may not have the ability to change the lighting settings of controldevice 214 and may be notified via a user device (e.g., user device 612)that occupant A 1414 is unable to change the lighting settings. In someembodiments, occupant A 1414 is notified via the user interface 702(e.g., through images on electronic display 706, audio from speakers710, etc.) that occupant A 1414 does not have permission to adjust thelighting settings.

Occupant A 1414, occupant B 1416, and occupant C 1418 may havepermissions and preferences for shades/blinds 1426. In some embodiments,occupant A 1414 has the preference that natural light be used toilluminate the zone which occupant A 1414 occupies whenever possible.Using natural light may include opening shades, opening blinds, and/oropening shutters. Occupant B 1416 and occupant C 1418 may have nopermission to open and/or close shades, blinds, and/or shutters. Anyattempt by occupants B 1416 and occupant C 1418 to open and/or closeshades, blinds, and/or shutters controlled by control device 214 may bemet with a notification that occupants A 1416 and/or occupant C 1418 maynot have the proper permission to open and/or close the shades, blinds,and/or shutters.

In some embodiments, control device 214 may disable changes to theshades and/or blinds whenever occupants B 1416 and/or occupant C 1418are determined to be a set distance from control device 214. In someembodiments, control device 214 may disable changes to the shades and/orblinds whenever occupants B 1416 and/or occupant C 1418 are identifiedin the zone which control device 214 is located. In some embodiments,when occupants B 1416 and/or occupant C 1418 are authenticated withbuilding management system 610 and/or control device 214 via a userdevice (e.g., user device 612) as described with reference to FIG. 14A,occupants B 1416 and/or occupant C 1418 may be notified via a userdevice (e.g., user device 612) that occupants B 1416 and/or occupant C1418 are unable to change the shades and/or blinds. In some embodiments,occupants B 1416 and/or occupant C 1418 are notified via the userinterface 702 (e.g., through images on electronic display 706, audiofrom speakers 710, etc.) that occupants B 1416 and/or occupant C 1418 donot have permission to adjust the shades and/or blinds.

Display and Emergency Features

Referring now to FIGS. 15 and 16A, a diagram 1500 and flowchart 1600illustrating a control process which may be performed by emergencymodule 756 and/or building module 746, according to some embodiments.Control device 214 may receive a weather forecast 1502 from a weatherserver 608 (step 1602) and display the weather forecast 1502 via userinterface 702 of control device 214 (step 1604). Control device 214 mayilluminate ambient lighting 1512 of control device 214 in response tothe weather forecast 1502 indicating a weather-related warning (step1606). In some embodiments, audio 1514 may be generated when the weatherforecast 1502 indicates a weather-related warning. The audio can be asiren, a warning message, and/or any other emergency related audio.Control device 214 may determine an adjustment to a control signal 1510for HVAC equipment 738 based on the weather forecast (step 1608).Control device 214 may generate and provide an adjusted control signal1510 to HVAC equipment 738. In some embodiments, the control signal 1510may cause shutters and/or doors to automatically close. The controlsignal 1510 may cause building sirens (e.g., speakers 504) to playemergency related audio (e.g., “Please evacuate the building”, “Takeshelter away from windows”, etc.)

Referring now to FIG. 16B, a flowchart of process 1612 illustrating thepropriety of message data streams is shown, according to an exemplaryembodiment. In some embodiments, process 1612 may be operated by controldevice 214 as described with reference to FIG. 7. In step 1614, controldevice 214 receives messages (e.g., general messages, emergencymessages, etc.) based on a data stream from the building managementsystem (e.g., building management system 610). Control device 214 may beconfigured to display general messaging (e.g., zone temperatures,building events, etc.) and/or emergency information on user interface702 based on a data stream received from building management system 610.

In some embodiments, if a connection is lost between control device 214and building management system 610, control device 214 may displaymessages stored and/or generated locally on control device 214 (step1616) on user interface 702. In some embodiments, the display messagesstored and/or generated locally on control device 214 include zonetemperatures, zone humidity, building events, etc. In the event that anemergency is detected by emergency sensors (e.g., building emergencysensor(s) 606) connected to control device 214, the general messagesreceived from building management system 610 may be overridden andemergency messages may be display on user interface 702 based on datareceived from the emergency sensors (step 1618). In some embodiments,when the data received from the emergency sensors is above a predefinedthreshold and/or below another predefined threshold, an emergency may beidentified. In the event that an emergency is detected by emergencysensors (e.g., building emergency sensor(s) 606) connected to controldevice 214, the general messages stored locally and/or determined bycontrol device 214 may be overridden and emergency messages may bedisplay on user interface 702 based on data received from the emergencysensors.

In some embodiments, control device 214 may receive a message from aweather server (e.g., weather server 608). Control device 214 may beconfigured to override general messages received from buildingmanagement system 610 when a notification for weather related emergencyand/or any other type of emergency is received from weather server 608(step 1620). Control device 214 may be configured to display weatherrelated emergency notifications and directions via user interface 702over the general messages received from building management system 610.

Referring now to FIG. 17, a drawing of a device displaying an emergencyscreen 1700 during an emergency situation is shown, according to anexemplary embodiment. In some embodiments, emergency screen 1700 may bedisplayed by control device 214. Emergency screen 1700 is shown toinclude an alert title 1702, an alert icon 1704, instructions 1706,directions 1708, and menu option 1710.

Emergency screen 1700 is shown to have an alert title 1702 describingthe contents of the page. In this exemplary embodiment, the title is“TORNADO WARNING.” In some embodiments, alert title 1702 is customizableto provide more information. In other embodiments, alert title 1702 iscustomizable to provide less information. Alert title 1702 may be abutton which takes the user to a page related to the title. For example,clicking alert title 1702 may take a user to a menu of pages related to“TORNADO WARNING.” In some embodiments, clicking and/or pressing alerttitle 1702 navigates to a website and/or other entity. The website maybe a weather server and may provide more information into the nature ofthe emergency.

Emergency screen 1700 is also shown to have an alert icon 1704. In thisexemplary embodiment, alert icon 1704 is an image of a tornado. Alerticon 1704 may be any symbol, text, etc., and indicates the nature of thealert. For example, alert icon 1704 may be an image of a snowflake, textreading “FLOOD,” text reading “FIRE,” text reading “ACTIVE SHOOTER,”etc. Alert icon 1704 provides information to a user about the alert, andmay be any indicator relating to any type of emergency.

Emergency screen 1700 is shown to have instructions 1706. Instructions1706 can provide information to a user about how to proceed in thecurrent situation. In some embodiments, instructions 1706 may inform auser of how to exit a building. For example, instructions 1706 mayinform a user of which room to head to. In other embodiments,instructions 1706 inform a user of which authorities to inform, etc. Forexample, instructions 1706 may instruct a user to call an ambulance,then the police, then building and/or campus security. Instructions 1706may be downloaded from a network (e.g., network 602). In someembodiments, instructions are requested from network 602. In variousembodiments, instructions are pushed to control device 214. Instructions1706 may be stored for access by control device 214 in specificsituations. In some embodiments, instructions 1706 may be stored locallyon control device 214. In other embodiments, instructions 1706 may bestored remotely from control device 214. Instructions 1706 may be storedanywhere and retrieved by control device 214.

Emergency screen 1700 is also shown to have directions 1708. In someembodiments, directions 1708 may be an embodiment of instructions 1706.In other embodiments, directions 1708 provide different information frominstructions 1706. Directions 1708 may provide a user informationregarding where to go. For example, directions 1708 may be an arrowpointing in the correct direction to go. In some embodiments, controldevice 214 is portable, and may detect movement to alter directions1708. For example, directions 1708 may change depending on the directiona user is facing. Directions 1708 may be any indicator providingdirectional information, and is not limited to those specificallyenumerated.

Emergency screen 1700 is also shown to have a menu option 1710. In thisexemplary embodiment, option 1710 is an “Ok” button. For example, option1710 may accept the prompt. In some embodiments, option 1710 may simplydismiss the prompt. In other embodiments, option 1710 may proceed to thenext action. In some embodiments, option 1710 is a forward button, amenu, etc. Option 1710 may perform any function, and is not limited tothose specifically enumerated.

Referring now to FIG. 18, an emergency screen 1800 of an evacuationroute is shown, according to an exemplary embodiment. In someembodiments, emergency screen 1800 is displayed by control device 214.Screen 1800 is shown to include position indicator 1802, floorplan 1804,and directions 1806. Screen 1800 may include other elements andcomponents, and is not limited to those specifically enumerated.

Screen 1800 is shown to include position indicator 1802. Positionindicator 1802 may provide information on the whereabouts of a user, oranother person, item, component, etc. For example, in this exemplaryembodiment, position indicator 1802 is shown as an image of a person,and indicates the position of the person. In some embodiments, positionindicator 1802 may indicate the position of multiple users, items, etc.Position indicator 1802 may further include a differentiating label,which may indicate which user, item, etc. is shown by each of themultiple indicators. In other embodiments, position indicator 1802 mayindicate the position of a single user, item, etc. Position indicator1802 may be any symbol, text, etc., and is not limited to thosespecifically enumerated.

Screen 1800 is shown to include floorplan 1804. Floorplan 1804 may be adiagram of a floorplan of an area serviced by control device 214. Insome embodiments, the area is the area in which control device 214 isinstalled. In other embodiments, the area is another area, and may beselected by a user. In some embodiments, floorplan 1804 may showmultiple locations. For example, floorplan 1804 may show both floors ofa two-story building. A user may be able to select multiple locations todisplay (e.g., the top floor and the fourth floor of a 35 storybuilding). In other embodiments, floorplan 1804 may show a singlelocation. Floorplan 1804 may display any number of any locations, and isnot limited to those specifically enumerated.

Screen 1800 is also shown to include directions 1806. Directions 1803may provide information to a user regarding how to navigate to a certainlocation (i.e., evacuate). In some embodiments, directions 1806 providethe fastest route out of a building. For example, directions 1806 maydirect a user to the exit of a building in case of an emergency. Inother embodiments, directions 1806 provide a user with a route to aspecified location. For example, directions 1806 may direct a user to ashelter (e.g., a basement fallout shelter, a safe location with nowindows, etc.) In yet other embodiments, directions 1806 may allow auser to select options for the route. For example, a user may be able toindicate that she wishes to stay on the same floor, avoid stairs, etc.In yet other embodiments, directions 1806 may enable a user to selectmultiple destinations. For example, a user may indicate that he wishesto stop by a supply room before continuing to a conference room. Theuser may be able to make edits to any selections made. Directions 1806are not limited to those forms and features specifically enumerated.

Referring now to FIGS. 19-20, a diagram 1900 and flowchart 2000illustrating a control process which may be performed by voice controlmodule 748 is shown, according to an exemplary embodiment. In someembodiments, flowchart 2000 is performed by voice command module 744.Control device 214 may receive a voice command 1904 from a user 1902(step 2002) via a microphone (e.g., microphone 726) and may determinethat the voice command 1904 contains a request to compile a grocery list(step 2004). In some embodiments, the voice command 1904 may be aconcierge question as described with reference to FIGS. 30-32. Controldevice 214 may compile a grocery list 1906 based on the voice command1904 received from the user 4102 (step 4156). In some embodiments,control device 214 replies to a concierge questions via a speaker (e.g.,speaker 710). In some embodiments, control device 214 is configured tosend a grocery order 1908 to a grocery service 1910 (step 2008) andreceive an order confirmation 1912 from the grocery service 1910 (step2010). Control device 214 may provide an audio feedback 1914 indicatingthat the grocery list has been updated and/or that the grocery order hasbeen placed. In various embodiments, the grocery list can be updatedand/or an order can be placed through touch based input. In someembodiments, the steps of flowchart 2000 can be performed by touchingbuttons on a touch screen associated with control device 214.

Health Care and Hospital Features

Referring now to FIG. 21, control device 214 is shown to communicate tovarious health care devices and systems, according to an exemplaryembodiment. In some embodiments, healthcare module 752 facilitateshealthcare functions of control device 214. Control device 214 shown tointeract with healthcare sensors 604, user device 612, buildingmanagement system 610, medical server 2102 and network 602. In someembodiments, control device 214 communicates with healthcare equipment2104. In various embodiments, the healthcare module 752 communicateswith healthcare equipment 2104 directly and/or via network 602. In someembodiments, healthcare equipment 2104 is shown to include life supportdevices 2106, hospital/clinic devices 2108, home medical devices 2110,or implantable medical devices 2112 (e.g., pacemakers, cardioverterdefibrillators, etc.).

Healthcare module 752 facilitates healthcare functionality of controldevice 214. Functions performed by healthcare module 752 may includemonitoring the health of occupants of the area in which controller 468is installed. In some embodiments, healthcare module 752 may monitor anoccupant's health through data collected by healthcare sensors 604and/or may determine a health metric for the occupant based on the datacollect by healthcare sensors 604. For example, healthcare module 752may monitor an individual's health by tracking his temperature throughhealthcare sensor 604. In some embodiments, healthcare sensor 604 is oneor more or a combination of a smartwatch, a smart wrist band, a heartrate monitor, a pacemaker, a portable insulin device, and/or any otherwearable medical device. In some embodiments, healthcare sensor 604 is acamera, an infrared camera, and/or any other occupancy detection device.Healthcare module 752 may use healthcare sensors 604 to monitor a user'swaking/rest times, heart rate, insulin levels, body temperature, etc.Healthcare module 752 is not limited to monitoring the health attributesspecifically enumerated, and may monitor any aspect of a user'sbio-status. In some embodiments, control device 214 is configured toforward any data collected by healthcare sensors 604 and/or healthcareequipment 2104 to medical server 2102. In some embodiments, medialserver 2102 is a hospital server, a nurses station computing system,and/or an emergency response operator server.

Healthcare module 752 may communicate with user interface 702 or userdevice 612 belonging to a user to sense and collect health data. Forexample, healthcare module 752 may communicate with an individual'ssmartwatch which contains a heart rate monitor to track the individual'sheart rate. In some embodiments, control device 214 does not communicatewith healthcare sensors 604 which monitor a user's health, and insteadcollects data solely from healthcare equipment 2104. In otherembodiments, control device 214 contains sensors and collects data fromother devices, combining the data collected to produce a general metricof a user's health.

Healthcare module 752 may detect a change of a predetermined amount or asensor value over or under a predetermined threshold value (e.g.,abnormally high and/or low heart rate (i.e., bradycardia andtachycardia), abnormally high and/or low insulin level, abnormally highand/or low temperature, etc.). In some embodiments, healthcare module752 may monitor the heart rate of an occupant and determine if the heartrate is abnormal (i.e., arrhythmia). In some embodiments, healthcaremodule 752 may alert a user, the monitored occupant, a nurse's stationcomputing system, a hospital server, a hospital computing system, call911 (i.e., send a message to an emergency response server and/or anemergency response computing system) etc. For example, healthcare module752 may communicate with user device 612 of a user to display an alertdescribing the situation triggering the healthcare alert. Healthcaremodule 752 may communicate with network 602 to update a healthcaresystem (e.g., medial server 2102) with new data collected, set a flag ona user's condition, etc. For example, healthcare module 752 may senddata to a patient database and update a value for a body temperature,blood pressure, etc.

In some embodiments, a heart rate and/or body temperature is measured bya smart wrist band and/or smart watch (e.g., healthcare sensors 604).The heart rate and/or body temperature (e.g., health data 4004) may besent to control device 214. In some embodiments, healthcare sensors 604are cameras. The cameras may be heat sensitive. The heat images (e.g.,health data 4004) may be sent to control device 214. Control device 214may determine the body temperature of various occupants of a building(e.g., building 10) based on the heat images (e.g., health data 4004)received form healthcare sensors 604.

Healthcare module 752 may send push alerts to user device 612 fromnetwork 602. For example, network 602 may receive a notification that itis time for a middle school individual to take her medication. Controldevice 214 may communicate with user device 612 of the individual, ateacher, a nurse, etc. to alert the user of user device 612 that it istime for the individual to take her medication. In some embodiments,control device 214 may communicate with a user through user interface702 to convey healthcare information. For example, network 602 mayreceive a notification that it is time for an individual's appointmentwith the nurse. Network 602 may communicate with control device 214 toconvey the information to the nurse, the individual, the individual'scurrent teacher, etc. For example, control device 214 may have access toa user's schedule and/or calendar, and adjust actions accordingly. Insome embodiments, control device 214 may determine that an individual iscurrently in math class, and may send an alert to user device 612 of theindividual. In other embodiments, control device 214 may determine thatan individual is currently in a free period with a specific teacher in aspecific room, and may send an alert to a control device 214 installedin the room, or to a user device 612 of the teacher. Control device 214may convey healthcare information through any media, and is not limitedto those specifically discussed.

Healthcare module 752 may contain some or all of the features ofoccupancy module 754. The occupancy detectors (e.g., healthcare sensors604, sensors 714, etc.) may be installed in a patient room in a healthcare facility and may be used to monitor the presence of the patient inthe room. Healthcare module 752 may communicate with the network 602,medical server 2102, and/or building management system 610 to alertmedical personnel if a patient leaves their room without permission.Healthcare module 752 may communicate with a user interface to determinethe identities of persons in a patient's room. For example, theoccupancy detector may use a camera and facial recognition software todetermine the identities of medical personnel that are present.Healthcare module 752 may use camera and facial recognition to determinethe presence of visitors and other unauthorized personnel in a patient'sroom.

In some embodiments, the healthcare module 752 communicates with usersor relevant persons when an emergency situation arises (e.g., buildingmanagement system 610, medical server 2102, user device 612, etc.)Healthcare module 752 may receive the patient's health information fromthe network, healthcare sensors 604, and/or healthcare equipment 2104,and display it to medical personnel if a medical alert is detected(e.g., abnormal blood pressure, abnormal oxygen saturation, abnormalheart rate, abnormal heart rhythm, etc.). In another embodiment,healthcare module 752 may communicate to the patient or to medicalpersonnel when a regular medical procedure is scheduled. For example,healthcare module 752 may communicate to the patient or to medicalpersonnel when a pill is to be taken, when an IV is to be replaced, whena wound dressing is to be changed, etc. In another embodiment,healthcare module 752 may communicate with alert module to communicatewith user device 612 of a patient. For example, if a patient isundergoing treatment requiring regular pill taking may receive alertsfrom an alert module on a mobile device (e.g., a smartphone, smartwatch, wearable, laptop, etc.).

Healthcare module 752 may communicate with any systems, devices, etc.connected to control device 214. For example, healthcare module 752 mayissue an alert to medical personnel which is pushed to control device214 (e.g., a nurse's station) and mobile devices (e.g., user device 612of medical personnel assigned to the patient, etc.) Healthcare module752 may issue an alert which is pushed to mobile devices 612 throughnetwork 602. Healthcare module 752 may be in communication with allmodules of control device 214.

In some embodiments, healthcare module 752 may require the credentialsof healthcare personnel to make changes related to treatment of thepatient. The healthcare module 752 may record the unique identity of anyuser making changes to a patient's treatment.

Referring now to FIGS. 22 and 23, drawings of control device 214communicating with other control devices 468 are shown, according toexemplary embodiments. In some embodiments, other control device 214 maybe located locally, such as in another room of the same building. Forexample, referring to FIG. 22, control device 214 is located in apatient's room in a hospital. Control device 214 may communicate withanother control device 214 at a nurse's station in the same hospital.The control device 214 may be directly connected and may communicatedirectly with each other. In another embodiment, the control device 214may be connected via a network.

In various embodiments, other control devices 468 are located remotely,such as in other buildings, states, countries, etc. For example,referring to FIG. 23, control device 214 in a patient's home or anassisted living facility may communicate with control device 214 at ahospital to facilitate out-patient care of the patient. Other controldevices 468 may be located anywhere relative to control device 214, andare not limited to locations specifically discussed or described.

In an exemplary scenario, a patient may be discharged from a medicalcare facility, such as a hospital to their home or to an assisted livingfacility. The patient may, for example, have received a routine checkupor may have been treated for a chronic or acute medical situation. Thepatient may be automatically monitored by healthcare equipment 2104 asdescried with reference to FIG. 21 after being discharged using one ormore control device 214 provided in the patient's home or assistedliving facility. The patient's health may be monitored using implantablemedical devices 2112 or home medical devices 2110 to allow remotemedical personnel to monitor the post care recovery of the patient.Control device 214 may be utilized to facilitate continuing medical care(e.g., physical therapy, medication schedule, follow-up visits to amedical facility, etc.).

Control device 214 may continue to monitor the health of the patientafter receiving medical care. If control device 214 detects a medicalalert, it may take an action, depending on the severity of the medicalalert. For example, control device 214 may prompt the patient to returnto the hospital, alert a local medical personnel (e.g., an in-home nurseor caretaker), or may have an ambulance sent to the patient's location.

In some embodiments, control device 214 can transmit patient data to acentral computer system (over a local network or via the internet) incompliance with HIPPA standards and regulations.

In some embodiments, control device 214 may not collect personal healthdata without consent of the person whose data is being collected. Inother embodiments, control device 214 may offer an opt-out system, wherecontrol device 214 is prevented from collecting personal health datawhen a user specifically opts out. In yet other embodiments, controldevice 214 may collect data from all users, and anonymize all databefore storing, analyzing, etc. For example, control device 214 maycollect data from all patients undergoing a particular procedure andanonymize all data before sending to a research facility, hospital, etc.

Control device 214 may collect data from each person, and each person isgiven a window of time to opt-out out retroactively or delete data. Insome embodiments, control device 214 may communicate with the usersthrough the user interface, a mobile devices, and/or the network toinform users that their data has been collected. For example, controldevice 214 may push a notification out to all applicable users over thenetwork that his or her information has been collected, and will bestored or sold to a hospital within 24 hours. In some embodiments usersmay be given the full 24 hours to opt-out or delete data. In otherembodiments, users may be given any predetermined period of time inwhich to respond or take action.

Control device 214 may communicate with users to ask for permission toshare his or her information. For example, control device 214 maydisplay a prompt on a mobile device of each person whose data wascollected. In some embodiments, control device 214 may share a user'sdata when permission has been granted. In other embodiments, controldevice 214 may share non-sensitive user data that has been anonymized.

Referring now to FIG. 24, a diagram of scenario 2400 in which controldevice 214 monitors an individual's 2408 health is shown, according tosome embodiments. In part 2402, control device 648 is shown tocommunicate with an individual 2408 via audio, visual items on a screen,a device, etc. The device may be a smartphone, smart watch, fitnesstracker, etc. In other embodiments, the device may be a medical device,such as a pace maker, insulin pump, etc. The device may be any device,and is not limited to those specifically enumerated.

The individual 2408 may communicate directly with control device 214through a user interface, voice commands, etc. For example, individual2408 may tell control device 214 that he does not feel well. In someembodiments, control device 214 may trigger an alert or take some otheraction depending on the information received. In other embodiments,control device 214 may wait for specific instructions to take actionbefore executing any commands.

In part 2404, a screen of control device 214 during normal healthmonitoring operation is shown. Control device 214 has confirmed thatindividual's 2408 body temperature, displays the temperature, theindividual's name, an indication that all is well, and takes no furtheraction. In some embodiments, control device 214 stores the information.In other embodiments, control device 214 sends the information tohealthcare institutions, facilities, professionals (e.g., medical server2102, building management system 610, etc.) Control device 214 mayhandle all information in accordance with HIPAA rules and regulations.

Control device 214 may monitor and collect any health data, such asblood pressure, heart rate, etc. For example, control device 214 maycommunicate with a heart rate monitor, and raise an alarm if anindividual's heart rate becomes irregular, over a threshold rate, etc.For example, control device 214 may detect that an individual isexperiencing a high amount of stress using a combination of bodytemperature and heart rate. Control device 214 is not limited to thehealth statistics specifically enumerated.

In part 2406, control device 214 has automatically detected that ahealth condition has arisen. In this exemplary depiction, the healthcondition is a fever, detected by the high body temperature. In otherembodiments, the health condition may be high stress, arrhythmia, lowblood sugar, etc. Control device 214 may produce a sound, vibrate, flashthe screen, etc. to present an alert to a user. In some embodiments,control device 214 may send a signal to a user device (e.g., user device612, network 602, building management system 610, medical server 2102,etc.) or some other system or device to display the alert, as describedabove.

Referring now to FIG. 25, a drawing of a screen 2500 displayed when anindividual is in distress is shown, according to an exemplaryembodiment. Screen 2500 is shown to include a live feed 2502 of theparticular individual. In some embodiments, live feed 2502 may be a mapor floorplan indicating where the individual is located. In otherembodiments, live feed 2502 may be a still photo of the individual tohelp healthcare professionals locate the individual.

Screen 2500 further includes an alert message 2504 and a cause 2506.Alert message 2504 may display any message, such as “STUDENT COLLAPSE,”“STUDENT EMERGENCY,” etc. In some embodiments, alert message 2504 may becustomized to provide more information, such as the individual's name,emergency contact information, etc. In other embodiments, alert message2504 may be customized to display anything that may be more helpful orappropriate for the environment in which user control device isinstalled. Alert message 2504 is not limited to those messagesspecifically enumerated.

Cause 2506 may be any reason, such as “Cardiac distress,” “Low bloodsugar,” etc. In some embodiments, cause 2506 may be customized toprovide more information, such as the individual's name, emergencycontact information, etc. In other embodiments, cause 2506 may becustomized to display anything that may be more helpful or appropriatefor the environment in which user control device is installed. Cause2506 is not limited to those messages specifically enumerated.

Screen 2500 is further shown to include an icon 2508. Icon 2508 may givea user a quick impression of what the alert is related to. Controldevice 214 is capable of providing alerts for many different categories,such as inclement weather, security, health, etc. Control device 214 isnot limited to those categories specifically enumerated. Icon 2508 maybe a symbol, a word, etc., and may be any indication of what the alertis related to.

Screen 2500 is further shown to include a location 2510. Location 2510may give a user the location of the particular individual to which thealert is related. In some embodiments, location 2510 is provided astext. In other embodiments, location 2510 is provided as a map. Forexample, location 2510 may be displayed as live feed 2502. Location 2510may be displayed or presented to the user in any form, and is notlimited to those specifically enumerated.

Screen 2500 is finally shown to include options 2512, 2514, and 2516.Options 2512, 2514, and 2516 may provide a user with options of actionsto take. In some embodiments, screen 2500 may include more options. Inother embodiments, screen 2500 may include fewer options. The optionspresented may be customized to be more appropriate for each situation.For example, if an individual's insulin pump needs to be restarted,control device 214 may present the option of restarting the pump. Insome embodiments, option 2516 to ignore the alert may not be available.For example, if an individual is in critical condition, such as cardiacarrest, user control device may automatically execute options 2512 and2514 by calling security and 911.

Concierge and Hotel Features

Referring now to FIG. 26A, a diagram of control device 214 is shown foruse in a hotel, according to an exemplary embodiment. In someembodiments, control device 214 receives concierge information frombuilding management system 610. In some embodiments, the conciergeinformation may include local attractions, local restaurants, and/or anyother concierge related information. In some embodiments, hotel module750 is configured to cause control device 214 to send a request forspecific concierge information to building management system 610 vianetwork 602 when a user requests concierge information via userinterface 702 and/or microphone 726. In some embodiments, hotel module750 may cause control device 214 to search for concierge information viathe Internet (e.g., network 602) if the building management system doesnot have the requested concierge information.

In some embodiments, hotel module 750 is configured to process ordersfor food from local restaurants. In some embodiments, control device 214(i.e., hotel module 750) may send a request to a restaurant computingsystem 2602 for a menu. Control device 214 may display the menu to theuser via user interface 702 and may allow the user to order fooddirectly through user interface 702 (i.e., enter orders through userinterface 702). In some embodiments, the user may be able to send areservation request to restaurant computing system 2602 via hotel module750 and display device 702. A user may place an order via user interface702 causing hotel module 750 to communicate with restaurant computingsystem 2602 via network 602. Hotel module 750 may cause payment module758 to process any payment transactions for food orders with financialinstitution system 3504. Payment transactions are described in furtherdetail at FIGS. 35-39.

In some embodiments, hotel module 750 is configured to process requestsfor taxis, busses, subways, trains, and/or planes. In some embodiments,control device 214 communicates with transportation server 2604.Transportation server 2604 may be Uber, Lyft, and/or any other taxiservice. In some embodiments, transportation server 2604 is an airlineserver, a buss server, a train server, etc. Hotel module 750 may allow auser to request a ride from transportation server 2604 and may causepayment module 750 to process payment transactions via network 602 andfinancial institution system 3504. In some embodiments, input device 712may be configured to scan credit and/or debit cards for payment fortransactions with restaurant computing system 2602 and/or transportationserver 2604. In some embodiments, payment module 758 facilitates thetransaction with financial institution system 3504. Input device 712 isdescribed in further detail in FIGS. 35-39.

Referring now to FIG. 26B, a process 2606 for scheduling a stay at ahotel is shown, according to some embodiments. In some embodiments,process 2606 is performed by hotel module 750 of control device 214.Process 2606 may be applied to scheduling any event, and is not limitedto hotels, cruises, etc. Process 2606 begins with step 2608, in which auser provides input to a control device 214. The user may provide inputthrough any means. For example, the user may provide input by voicecommand, tactile input to a user interface (e.g., user interface 702),gesture input, input to a mobile device (e.g., user device 612), etc.

According to this exemplary embodiment, a calendar interface may beprovided to a user via the user interface and/or the mobile device. Insome embodiments, the calendar interface may show the user'sappointments and events. For example, a user's work and personalcalendar events may be displayed on the calendar interface. In otherembodiments, multiple users' schedules may be displayed on the calendarinterface.

The calendar interface may show information such as availabilities for ahotel. In some embodiments, the control device 214 is located inside thehotel which it displays availability for. In some embodiments, thecalendar interface may provide all availabilities. In other embodiments,the calendar interface may be sorted according to room size, amenities,etc. The calendar interface may not be specific to a single hotel. Insome embodiments, the calendar interface may display availabilities formultiple hotels. The hotels shown may be selected by a user. In otherembodiments, control device 214 may automatically select multiple hotelsaccording to criteria such as price range, length of stay, amenities,distance to destinations, hotel ratings, etc.

The information may be displayed in any format. For example, controldevice 214 may display the information as drop-down boxes, check boxes,etc. In some embodiments, control device 214 may display contentdirectly from a hotel's website, a travel website, etc. In otherembodiments, control device 214 may display content parsed from awebsite, in a format native to control device 214.

Process 2606 continues with step 2610, in which a user selects a rangeof days for her stay at the hotel. In some embodiments, a user selects arange of consecutive days. In other embodiments, a user may select a setof non-consecutive days. The user may enter other information, such asbilling information, number of guests, destination, etc. In someembodiments, the calendar interface may display the range of daysselected as darkened days, checked boxes, etc. The information input bythe user is transmitted from control device 214 to a building managementsystem for a hotel (e.g., building management system 610) and/or anyother server for the hotel.

Process 2606 continues with step 2612, the information transmitted fromcontrol device 214 is received by a database. In some embodiments,control device 214 may book a stay at the hotel directly using enteredbilling information. In other embodiments, control device 214 connectsthe user to a travel agent, to the hotel's booking website with thefields pre-populated, etc. The information transmitted from controldevice 214 may be received by any system, and is not limited todatabases. In some embodiments, the database is connected to a hotel'smain system, and hotel staff are notified. In some embodiments, thehotel's main system is building management system 610.

The database may be connected to additional services, such asdestinations, airlines, etc. For example, control device 214 mayautomatically suggest flights from a billing address entered by the userto the destination entered by the user. In some embodiments, controldevice 214 may automatically select flights and present the user with aconfirmation dialog. In other embodiments, control device 214 presents aset of available flights for the scheduled hotel stay. Control device214 may also suggest, book, etc. activities, such as local attractions,tours, ground transportation, etc.

Control device 214 may learn from information entered by the user withhis permission. For example, control device 214 may store informationsuch as a user's preferences for flight times, direct vs. non-directflights, seat preferences, hotel chain preferences, pillow firmnesspreferences, attractions, tours, ground transportation, etc. A user maybe presented with a dialog confirming that she is allowing controldevice 214 to store or analyze such data. In some embodiments, the datais stored remotely. In other embodiments, the data is stored locally oncontrol device 214.

Process 2606 continues with step 2614 in which control device 214provides the user with information. In some embodiments, control device214 provides a confirmation of all bookings made. In other embodiments,control device 214 provides a list of prospective bookings, contactinformation for each option, etc. Control device 214 may provide theuser with any information. In some embodiments, control device 214 maynot provide the user with further information.

In this exemplary embodiment, control device 214 is shown to provide theuser with information through a user interface (e.g., user interface702). In other embodiments, control device 214 may provide the user withinformation through any medium, format, etc. For example, control device214 may provide the user with information through speakers (e.g.,speakers 710), a mobile device (e.g., user device 612), etc.

Referring now to FIG. 27, a process 2700 for arranging transportationvia control device 214 is shown, according to some embodiments. In someembodiments, process 2700 is performed by voice command module 744and/or hotel module 750. Process 2700 begins with step 2702, in which auser is presented with a screen having options for arrangingtransportation. In some embodiments, process 2700 is performedautomatically. In other embodiments, a user may choose to enter atransportation mode to arrange transportation via control device 214.

Process 2700 continues with step 2704, in which control device 214 maypresent the user with a list of available modes of transportation. Forexample, control device 214 may present the user with a list of links todifferent sites of different modes of transportation. In someembodiments, each option is a link which takes the user to a set ofavailable options. Availability may be determined by criteria such asthe current time, the desired time, the location, the distance, the modeof travel, extra considerations for the passenger (oversize luggage,animals, etc.), etc. In some embodiments, the user may enter thecriteria via user interface 702. In various embodiments, the user mayenter the criteria via microphone 726 and voice command module 744.Control device 214 may suggest the closest form of transportation if theselected mode is unavailable. In some embodiments, control device 214may make suggestions and/or arrange the list of modes of transportation(i.e., most relevant mode of transportation to least relevant mode oftransportation) based on the most commonly used, least expensive,fastest, a target destination, etc. For example, if no taxis areavailable at the desired time, control device 214 may suggest taking thesubway.

Process 2700 continues with step 2706, in which control device 214 maymake arrangements for the final selection. For example, once the userhas selected the taxi company, times, options, etc., control device 214may place a call to the company to make arrangements. In someembodiments, control device 214 may enter the information in thecompany's website. In other embodiments, control device 214 may presentthe information to the user, who will make the final arrangementshimself.

Process 2700 continues with step 2708, in which the user is connectedwith her transportation. In some embodiments, the transportation travelsto pick up the user. In other embodiments, the user travels to board thetransportation. The travel arrangements may be made for travelling to adestination, travelling from a destination, etc. Travel arrangements maybe made for any purpose.

Referring now to FIG. 28, drawings of embodiments 2802, 2804, and 2806are shown illustrating options to set arrangement preferences, accordingto some embodiments. Some embodiments are useful in hotel arrangements.In other embodiments, a user may select preferences for anyarrangements, such as travel (e.g., flights, ground transportation,etc.). Embodiment 2802 shows a preferences interface displayed oncontrol device 214. Available options may include guest name,temperature preference, lighting preference, pillow firmness preference,housekeeping preference, etc. Any options may be available for a user toselect, and a user may be able to change her preferences. For example, auser may prefer low lighting in the summer and medium lighting in thewinter. Embodiment 2804 shows a preferences interface displayed on userdevice 612 of a user. Embodiment 2806 shows a preferences interfacedisplayed on a web browser.

Other ways of making arrangements may be available via control device214. In some embodiments, a user may be able to set preferences throughvoice command, gesture input, etc. In other embodiments, a user may setpreferences through specific applications, the hotel's website, etc. Insome embodiments, the control device 214 can send payment and/or creditcard information for the transportation. In some embodiments, hotelmodule 750 may process payment with input device 712 and payment module758.

Referring now to FIG. 29, a process 2900 is shown for preparing a hotelroom for a guest's stay, according to some embodiments. Process 2900begins with step 2902, in which a control device 214 installed in anunoccupied room is in a power-saving state. Control device 214 maydisplay relevant information for the room, such as the room number, thecurrent occupancy, the mode, and the current conditions. Control device214 may display more information. In some embodiments, control device214 may display less information. Control device 214 may be customizedto display the information needed for each situation.

Process 2900 continues with step 2904, in which control device 214receives reservation information for the room at a first time. Controldevice 214 may display a confirmation message. In some embodiments,control device 214 may send a confirmation message to the front desk,main system, etc. In other embodiments, control device 214 may send aconfirmation message to the user. In this exemplary embodiment, thereservation information is received at 1 p.m. local time, and thereservation is for 6 p.m. local time.

Process 2900 continues with step 2906, in which the reservationinformation and/or preferences are analyzed. The received informationmay include room number, temperature, humidity, lighting level, pillowfirmness, etc. Other information and preferences may be set. The formatin which the information is presented to the system, control device 214,etc. may be any format. For example, the system may receive theinformation as raw data while control device 214 receives data parsedinto packets for each category of preference.

Process 2900 continues with step 2908, in which control device 214 maydetermine the amount of time needed to reach the guest's preferredsettings, and when to begin preparing. Control device 214 may determinethe approximate time of arrival of a guest and the approximate amount oftime needed to reach the environmental setpoints of the guest.

Process 2900 continues with step 2910, in which control device 214 hasdetermined the amount of time needed, the time at which to beginpreparing, etc. For example, the preparation for a guest Jimmy arrivingat 6 p.m. is shown to begin at 4 p.m. Control device 214 may begin tochange the temperature, humidity, etc. of the room. For example, controldevice 214 may begin to heat the room from 69° F. to Jimmy's preferred70° F.

Process 2900 continues with step 2912, in which control device 214informs hospitality services of the guest's preferences. In thisexemplary embodiment, Jimmy prefers firm pillows. Control device 214 isshown to inform the front desk of Jimmy's preference. In someembodiments, control device 214 communicates directly with the frontdesk (e.g., a computer at the front desk). In other embodiments, controldevice 214 goes through an intermediary (e.g., network 602) tocommunicate with the front desk. Control device 214 may communicate withthe front desk through any means, and may transmit any information.Control device 214 may be compliant with all privacy rules andregulations.

Process 2900 continues with step 2914, in which control device 214communicates with hotel equipment (e.g., HVAC equipment 738) to achievethe guest's preferences. In this exemplary embodiment, Jimmy prefers lowlighting. Control device 214 may communicate with lights (e.g., HVACEquipment 738) of the room to dim. In some embodiments, control device214 may communicate directly with lights 2920. In other embodiments,control device 214 may communicate through an intermediary, such ashotel automation system (e.g., building management system 610), network602, etc. Control device 214 may communicate with hotel equipment (e.g.,HVAC Equipment 738) through any communications protocol, and is notlimited to those specifically enumerated.

Process 2900 continues with step 2916, in which the guest arrives at theroom at a time indicated by his reservation information transmitted tocontrol device 214. In this exemplary embodiment, Jimmy arrives at Room78 at 6 p.m. local time. Control device 214 is shown to display one ormore room settings. For example, control device 214 is shown to bemounted to a wall of the room, and displays the current roomtemperature—Jimmy's preferred 70° F. Lighting 2920 may be at Jimmy'spreferred low setting. In some embodiments, accommodations such as bedinclination level/mattress firmness (e.g., hotel module 750) may beadjusted. In other embodiments, fewer settings may be adjusted.

Process 2900 continues with step 2918, in which the guest is greeted bycontrol device 214. In some embodiments, control device 214 greets theguest purely visually. For example, control device 214 may display textsaying “Welcome to Room 12, Aaron.” In other embodiments, control device214 may greet the guest using sound. For example, control device 214 maysay “Welcome to Room 78, Jimmy.” Control device 214 may greet the userthrough any means. Control device 214 may be customizable to use agreeting a user has selected, or a greeting specific to the hotel, theroom, etc. the user is staying in. Control device 214 may provideoptions to the user, such as a call for room service, access to thefront desk, concierge, etc. In some embodiments, control device 214performs many of the functions of the concierge desk. In otherembodiments, control device 214 connects a user to the concierge desk.

Referring now to FIG. 30, a process 3000 is shown for communicating witha front desk in the event of a service call. In some embodiments,process 3000 is performed by voice command module 744 and/or hotelmodule 750. In some embodiments, the service call can be made via avoice command and/or through user interface 702. Process 3000 beginswith step 3002, in which a set of options available for a user to make aservice call regarding is shown on control device 214. In someembodiments, the options are displayed through another medium, such as amobile device (e.g., user device 612) of a user. Each option displayedmay be a link. In some embodiments, the link may take the user to a pagewith more information about the option. In other embodiments, the linkmay trigger the service call to be made.

Process 3000 continues with step 3004, in which the user chooses anoption and inputs the selection to control device 214. In someembodiments, the user may provide the input as a voice command. In otherembodiments, the user may provide the selection as a button press, atactile input, a gesture, etc via a user interface (e.g., user interface702). Any input method may be used.

Process 3000 continues with step 3006, in which the selection istransmitted from control device 214 to the appropriate system. In someembodiments, the appropriate system is building management system 610.For example, if the selection made is a request for new towels,housekeeping would be notified. In some embodiments, housekeeping may benotified via building management system 610. In some embodiments,selections made indicate that other departments, such as the front desk,billing, etc. are contacted. In some embodiments, the front desk andbilling are connected to building management system 610.

In other embodiments, the request made can be executed automatically bycontrol device 214. For example, if the user requests that the light beturned off when there are multiple lights in the room, control device214 may use voice command detection (e.g., voice control module 748).Control device 214 may detect which occupancy sensor (e.g., sensors 714)detected the user's voice, or which sensor detected the voice the“loudest.” Control device 214 may decide the location of the user usingan algorithm and turn off the light nearest that location.

Referring now to FIG. 31, a process 3100 is shown for utilizing aconcierge feature of control device 214, according to some embodiments.In some embodiments, process 3100 is performed by voice command module744 and/or hotel module 750. Process 3100 begins with step 3102, inwhich a user asks control device 214 “What time does the gym close?”Control device 214 may access the requested information. In someembodiments, the information is stored remotely from control device 214.In other embodiments, the information is stored locally on controldevice 214. In yet other embodiments, control device 214 may search forthe information, call the front desk, etc.

The user may request information in any way. In some embodiments, theuser may request information through voice commands. In otherembodiments, the user may request information through tactile input(e.g., via user interface 702), via a mobile device (e.g., user device612), etc.

Process 3100 continues with step 3104, in which user control device hasobtained the requested information, and transmits the information to theuser. In some embodiments, control device 214 provides the informationto the user through speakers. For example, control device 214 may say“The gym closes at 12 a.m.” In other embodiments, control device 214 maytransmit the information through text, images, etc. Control device 214may present the information to the user via a user interface (e.g., userinterface 702), a mobile device (e.g., user device 612), etc.

In some embodiments, control device 214 provides information to the userin the same way the user requested the information. For example, if theuser asked a question using a voice command, control device 214 wouldanswer the question via speakers. In other embodiments, control device214 may provide information to the user according to her preferences. Inyet other embodiments, control device 214 would answer the question viaa default method, which may be customizable.

Referring now to FIG. 32, a process 3200 is shown for utilizing aconcierge feature of control device 214, according to another exemplaryembodiment. In some embodiments, process 3200 may be performed by hotelmodule 750 of control device 214 and/or voice command module 744.Process 3200 begins with step 3202, in which a user asks control device214 “What are some local restaurants?” Control device 214 may access therequested information. In some embodiments, the information is storedremotely from control device 214. In other embodiments, the informationis stored remotely on building management system 604. In yet otherembodiments, control device 214 may search for the information on theInternet (e.g., via network 602), call the front desk, etc.

The user may request information in any way. In some embodiments, theuser may request information through voice commands. In otherembodiments, the user may request information through tactile input(e.g., via user interface 702), via a mobile device (e.g., user device612), etc.

Process 3200 continues with step 3204, in which user control device hasobtained the requested information, and transmits the information to theuser. In some embodiments, control device 214 provides the informationto the user through speakers. In other embodiments, control device 214may transmit the information through text, images, etc. if the answer istoo long or too complicated to answer over speakers. For example, if theinformation requested is an explanation for why the sky is blue, usercontrol device may, as a default, present the information to the userthrough text. Control device 214 may present the information to the uservia user interface 702, user device 612, etc.

Referring now to FIG. 33, a process 3300 for requesting accommodationinformation from control device 214 is shown, according to someembodiments. Process 3300 begins with step 3302, in which a userrequests information from control device 214. In some embodiments, theuser may request information via voice command. In other embodiments,the user may request information via a tactile input through userinterface 702, gesture input, etc. Control device 214 may access therequested information. In some embodiments, the information is storedremotely from control device 214. In other embodiments, the informationis stored locally on control device 214. In yet other embodiments,control device 214 may search for the information, call the front desk,etc.

The user may request information in any way. In some embodiments, theuser may request information through voice commands. In otherembodiments, the user may request information through tactile input(e.g., user interface 702), via a mobile device (e.g., user device 612),etc.

Process 3300 continues with step 3304, in which user control device hasobtained the requested information, and transmits the information to theuser. In some embodiments, control device 214 provides the informationto the user through speakers. In other embodiments, control device 214may transmit the information through text, images, etc. In thisexemplary embodiment, the information is presented through an interfaceof a companion application for control device 214. The exemplaryembodiment includes a room status indicator 3306. The exemplaryembodiment also includes a menu option 3308. The exemplary embodimentincludes a message 3310 that greets the user and provides relevantinformation. For example, if the user is leaving the hotel on that day,message 3310 may include the time of checkout.

The exemplary embodiment includes an information section 3312 thatprovides relevant information regarding attractions and accommodations.In some embodiments, the attractions and accommodations are local to thehotel. In other embodiments, a user may specify the location, distance,price, etc. Control device 214 may store the information. In someembodiments, control device 214 may access the information from anoutside site, such as Yelp, Google Reviews, etc.

The exemplary embodiment includes a navigation section 3314 thatprovides navigation tools. In some embodiments, the tools are buttonsrepresented by icons. In other embodiments, the tools may be text links,check boxes, etc. Navigation section 3314 may be customized to providerelevant options. The exemplary embodiment further includes a systemindicator 3316. The exemplary embodiment further includes a page title3318.

Process 3300 continues with step 3318, in which a screen showsaccommodations available at the hotel. A user may input a selectionthrough control device 214 by any means previously described.

Process 3300 continues with step 3320, in which a screen showing afloorplan is displayed on control device 214. In some embodiments, thefloorplan may display a user selection, such as a pool. In thisexemplary embodiment, the user selected the pool from the screen ofcontrol device 214. The location of the pool on the floorplan is shownon the screen. In other embodiments, other information may be shown oncontrol device 214, as described earlier.

Referring now to FIG. 34, a process 3400 is shown for assisting a userwith checkout without having to go to the front desk. Process 3400begins with step 3402, in which control device 214 presents a checkoutscreen to the user. In some embodiments, the screen is presentedautomatically at checkout time. In other embodiments, the screen may berequested by the user. The screen may include information such as theroom number, incidental charges, total charges, tip amounts, etc.Process 3400 may not proceed without confirmation from the user that theinformation presented is correct, and that she accepts all chargesshown.

Process 3400 continues with step 3404, in which control device 214thanks the user for staying with the hotel with a parting message. Insome embodiments, the parting message may be customized to the user'sliking. In other embodiments, the parting message is customized for thehotel. The parting message may be delivered in any way. In someembodiments, the parting message is delivered via speakers. In otherembodiments, the parting message is delivered as text, images, etc. Theparting message may be accompanied by a receipt for the total of thestay. In some embodiments, the receipt may be printed by control device214. In other embodiments, the receipt may be printed at the front deskand delivered to or picked up by the user. Process 3400 may be executedby control device 214 and/or hotel module 750.

In some embodiments, control device 214 prompts the user to enterpayment information and/or swipe a credit and/or debit card via inputdevice 712. This may allow the user to pay for their stay and/or anyadditional charges without stopping at the front desk. In someembodiments, the control device facilitates transfer of funds from afinancial account associated with a user to a financial accountassociated with the hotel. The financial account may be held withfinancial institution system 3504 and control device 214 may facilitatethe transfer of funds with hotel module 750 and payment module 758. Insome embodiments, the user is required to swipe their card with inputdevice 712 at the beginning of their stay and simply confirm the amountand/or leave a tip when their stay expires.

Payment Features

Referring to FIGS. 35-39, in some embodiments, control device 214 mayinclude payment features allowing a user to make payments with a varietyof different devices using a variety of different payment protocols. Forexample, control device 214 may be installed in any location in which auser may make a payment directly, without the involvement of a cashieror other worker, such as in a vehicle (e.g., a taxi), a parkingstructure, a public transportation station, a hotel, or a retaillocation (e.g., a store checkout line, a trade show, a convention,etc.).

Referring specifically to FIG. 35, payment module 758 is shown indetail. Payment module 758 is shown to interact with user interface 702,input device 712, financial institution system 3504, and network 602. Insome embodiments, payment module 758 may interact with a remote device3506. Remote device 3506 may be any device providing data related to afinancial transaction. For example, remote device 3506 may be a cashregister or terminal, a taximeter, a mobile device, or any other devicecapable of providing data related to a financial transaction. The remotedevice may be directly coupled to control device 214 and directlycommunicates with control device 214 with a wired or wirelessconnection. In some embodiments, remote device 3506 is coupled tocontrol device 486 through network 602 and communicates with controldevice 214 through the network 602.

Referring now to FIG. 36, a block diagram illustrating an input device712 of user control device 468 is shown, according to an exemplaryembodiment. Input device 712 is shown to include a card reading device3602. Card reading device 3602 may be any device that is able to receiveinformation from a card (e.g., credit card, debit card, gift card,commuter card, etc.).

Referring to FIG. 37, a diagram of a control device processing paymentwith an input device, according to an exemplary embodiment. In oneembodiment, card reading device 3602 may be a magnetic strip reader thatis configured to receive information encoded in a magnetic strip on thecard. Information encoded on a magnetic strip of the user's card may beread by the card reading device by inserting the card into the cardreading device or by swiping the card through the card reading device.In another embodiment, card reading device 3602 may be a chip readerthat is configured to receive information encoded on a microchip on thecard. Information encoded on the microchip of the user's card may beread by the card reading device by inserting the card into card readingdevice 3602. In another embodiment, card reading device 3602 may useanother technology to receive information encoded on the user's card.For example, card reading device 3602 may include an infrared scanningmechanism to read information encoded in a bar code on the user's card.

In some embodiments, input device 712 (e.g., card reader, wirelessreader, etc.) may be integrated into the user control device. Forexample, input device 712 may be integrally formed with the display orthe base. In other embodiments, input device 712 may be coupled to thedisplay or the base (e.g., as an aftermarket device, etc.). In otherembodiments, input device 712 may be separate from control device 214and may be connected to control device 214 through a wired connection ora wireless connection.

Referring now to FIG. 38, a diagram of control device 214 processing apayment with input device 712 is shown, according to an exemplaryembodiment. In FIG. 38, control device 214 is shown to include inputdevice 712 that is able to receive information from card 3802 (e.g.,credit card, debit card, gift card, commuter card, etc.) or user device612 without physically interacting with the card or mobile device usinga wireless protocol (e.g., ZigBee, Bluetooth, Wi-Fi, NFC, RFID, etc.).In one exemplary embodiment, a user may make a payment by passing adevice capable of NFC communication in close proximity to the usercontrol device to make a payment using a mobile payment service (e.g.,Apple Pay, Google Wallet, Android Pay, etc.).

Referring now to FIG. 39, a process 3900 for making a payment with usercontrol device 214 is shown according to some embodiments. In someembodiments, process 3900 is performed by payment module 758 of controldevice 214. Process 3900 begins with step 3902 in which transaction datais entered and the transaction data is communicated to control device214. In some embodiments, the transaction data may be entered directlyinto control device 214 with user interface 702. In some embodiments,the transaction data is received from a remote device. For example,transaction data may be received from a cash register, a paymentterminal, a taximeter, a mobile device, etc.

The process continues with step 3904 in which payment data is receivedby user control device 214. Payment data may be received, for example,by swiping a card through a card reader (e.g., input device 712, cardreading device 3602, etc.), inserting a card into a card reader, passinga card under a sensor (e.g., an infrared sensor), or holding a card ormobile device close to control device 214. The payment data may includevarious information such as authentication data, encryption data,decryption data, etc.

The process continues with step 3906 in which user control device 214communicates with financial institution system 3504 to authorize thepayment. Financial institution system 3504 may, for example, be a creditcard company or a banking network. The control device 214 communicates avariety of information to financial institution system 3504 includingpayment data and transaction data to authorize the payment.

CONFIGURATION OF EXEMPLARY EMBODIMENTS

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements may bereversed or otherwise varied and the nature or number of discreteelements or positions may be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepsmay be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions may be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Combinationsof the above are also included within the scope of machine-readablemedia. Machine-executable instructions include, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions.

Although the figures show a specific order of method steps, the order ofthe steps may differ from what is depicted. Also two or more steps maybe performed concurrently or with partial concurrence. Such variationwill depend on the software and hardware systems chosen and on designerchoice. All such variations are within the scope of the disclosure.Likewise, software implementations could be accomplished with standardprogramming techniques with rule based logic and other logic toaccomplish the various connection steps, processing steps, comparisonsteps and decision steps.

What is claimed is:
 1. A multi-function thermostat for a building, thethermostat comprising: a communications interface configured to:communicate with an emergency server; and receive occupant health datafrom one or more health sensors configured to monitor an occupant of thebuilding; and a processing circuit configured to: determine a healthmetric associated with the occupant based on the occupant health data;and cause the communications interface to send a distress message to theemergency server when the health metric associated with the occupantindicates a medical emergency.
 2. The thermostat of claim 1, wherein thecommunications interface is configured to communicate with occupancysensors; wherein the processing circuit is configured to identify theoccupant based on occupancy data received from the occupancy sensors. 3.The thermostat of claim 1, wherein at least one health sensors is asmart wrist band and the occupant health data comprises at least one ofa heart rate and a body temperature.
 4. The thermostat of claim 1,wherein the processing circuit is configured to determine the healthmetric associated with the occupant by: identifying a measured valueindicated by the occupant health data, wherein the measured valuecomprises at least one of a body temperature of the occupant, a heartrate of the occupant, and an insulin level of the occupant; comparingthe measured value to one or more stored threshold values; andgenerating the health metric based on a result of the comparing, whereinthe health metric indicates whether the measured value is above or belowone or more of the stored threshold values.
 5. The thermostat of claim1, wherein: the occupant health data comprises a measured heart rate ofthe occupant; and the processing circuit is configured to determine thehealth metric associated with the occupant by monitoring the occupanthealth data for heart arrhythmia.
 6. The thermostat of claim 1, wherein:the emergency server comprises at least one of an emergency responseoperator server, a nurses' station computing system, and a hospitalserver; and the distress message comprises a description of the medicalemergency associated with the occupant.
 7. The thermostat of claim 1,wherein the processing circuit is configured to push health messages toa user device, wherein the health messages comprise at least one of thedistress message, a reminder to take medication, and a reminder for anappointment.
 8. The thermostat of claim 1, wherein: the communicationsinterface is configured to communicate with a hospital server; and theprocessing circuit is configured to push the occupant health data to thehospital server via the communications interface.
 9. The thermostat ofclaim 1, further comprising a user interface; wherein the processingcircuit is configured to cause the user interface to display informationassociated with the medical emergency, the information comprising atleast one of a type of the medical emergency, a name of the occupant inneed of medical attention, and a location of the occupant in thebuilding.
 10. A method for operating a multi-function thermostat for abuilding, the method comprising: receiving occupant health data from oneor more health sensors via a communications interface of the thermostat:determining, by a processing circuit of the thermostat, a health metricassociated with an occupant of the building based on the occupant healthdata; and causing the communications interface to send a distressmessage to an emergency server when the health metric associated withthe occupant indicates a medical emergency.
 11. The method of claim 10,further comprising: receiving occupancy data from one or more occupancysensors via the communications interface; and identifying the occupantbased on occupancy data received from the occupancy sensors.
 12. Themethod of claim 10, wherein the health sensors comprise a smart wristband and the occupant health data comprises at least one of a heart rateand a body temperature.
 13. The method of claim 10, wherein: theoccupant health data comprises a heart rate; and determining the healthmetric comprises monitoring the occupant health data for heartarrhythmia.
 14. The method of claim 10, wherein the emergency servercomprises at least one of an emergency response operator server, anurses' station computing system, and a hospital server, and thedistress message comprises a description of the medical emergencyassociated with the occupant.
 15. The method of claim 10, wherein themethod further comprises causing a user interface to display medicalemergency information comprising at least one of the nature of a typemedical emergency, a name of the occupant in need of medical attention,and a location of the occupant in the building.
 16. The method of claim10, wherein the method further comprises causing the communicationsinterface to push the occupant health data received from the heathsensors to a hospital server via the communications interface.
 17. Amulti-function thermostat for a building, the thermostat comprising: acommunications interface configured to: communicate with an emergencyserver; and receive health data from a wearable health sensor; and aprocessing circuit configured to: determine a health metric associatedwith an individual wearing the wearable health sensor based on thehealth data received from the wearable health sensor; and cause thecommunications interface to send a distress message to the emergencyserver when the health metric associated with the individual indicates amedical emergency.
 18. The thermostat of claim 17, wherein the wearablehealth sensor comprises a smart wrist band and the health data comprisesat least one of a heart rate and a body temperature.
 19. The thermostatof claim 17, wherein the processing circuit is configured to determinethe heath metric by: monitoring the health data for heart arrhythmiawhen the health data comprises a heart rate; and monitoring the healthdata for tachycardia or bradycardia when the health data comprises aheart rate.
 20. The thermostat of claim 17, wherein the wearable healthsensor is an insulin pump and the health data comprises an insulin levelof the individual; wherein the processing circuit is configured to:compare the measured insulin level to one or more stored thresholdvalues; and generate the health metric based on a result of thecomparing, wherein the health metric indicates whether the measuredvalue is above or below one or more of the stored threshold values.